[linux-mm-cc] cant compile with 2.6.32 - Arch linux

Tibor Bamhor tibor.bamhor at netkosice.sk
Thu Jan 14 17:21:19 EST 2010


Nitin,
thanks for your answer.

So bottom line is that 2.6.33 kernel will not be usable (for compcache)  
without patching. This can be problem for some linux distributions, I mean  
to get your patches to official distribution kernel. Anyway I understand  
why it is.

In regard to the init script, in arch linux we have init script like:
/etc/rc.d/compcache start|stop|status
that basically uses your un/use_compcache.sh scripts, just to be somehow  
"standardized", like other "services" of system.
So necessity of such init script depends on a way how compcache is  
intended to be started in future... But I dont think this question needs  
attention now.


Thats all from me, thank for you attention

Tibor




On Mon, 11 Jan 2010 09:12:16 +0100, Nitin Gupta <ngupta at vflare.org> wrote:

> On Mon, Jan 11, 2010 at 10:37 AM, Tibor Bamhor
> <tibor.bamhor at netkosice.sk> wrote:
>> Thanks for information
>> This PKGBUILD (for arch linux) covers only compilation of modules - no
>> recompilation of kernel(too complicated). So it seems that it will not  
>> help
>> in this situation.
>>
>> Yet another questions, what exactly means that compcache will be in  
>> kernel
>> (from 2.6.33)? Will vanila kernel provide everything? Including modules  
>> that
>> are now compiled from sources downloaded from homepage?
>
> Vanilla kernel (2.6.33) contains all ramzswap code except a small
> portion of code
> which allows ramzswap to eliminate any stale data in memory. Without  
> this small
> piece of code, ramzswap can actually degrade system performance since  
> stale
> data can quickly accumulate in memory, defeating the whole purpose of  
> compressed
> caching.
>
> This small bit of code has now been accepted into '-mm tree', but not
> sure when it
> will be integrated in mainline Linux kernel.
>
> Since bulk of code is already in mainline, future release will simply
> be patches against
> this existing in-kernel code that implement functionality (or fixes)
> which are not yet
> included in mainline. Eventually, when all these bits enter mainline,
> there will be not
> separate release from project page.
>
>> For arch linux we
>> currently have an init script, will it still be needed?
>>
>
> Not sure what this script does.
>
> Thanks,
> Nitin
>




More information about the linux-mm-cc mailing list