OOM panics with zram
ngupta at vflare.org
Tue Oct 5 21:30:39 PDT 2010
On 10/5/2010 10:36 PM, Greg KH wrote:
> On Tue, Oct 05, 2010 at 10:29:34PM -0400, Nitin Gupta wrote:
>> On 10/5/2010 7:43 PM, Greg KH wrote:
>>> On Sun, Oct 03, 2010 at 02:41:09PM -0400, Nitin Gupta wrote:
>>>> Also, please do not use linux-next/mainline version of compcache. Instead
>>>> just use version in the project repository here:
>>>> hg clone https://compcache.googlecode.com/hg/ compcache
>>> What? No, the reason we put this into the kernel was so that _everyone_
>>> could work on it, including the original developers. Going off and
>>> doing development somewhere else just isn't ok. Should I just delete
>>> this driver from the staging tree as you don't seem to want to work with
>>> the community at this point in time?
>> Getting it out of -staging wasn't my intent. Community is the reason
>> that this project still exists.
>>>> This is updated much more frequently and has many more bug fixes over
>>>> the mainline. It will also be easier to fix bugs/add features much more
>>>> quickly in this repo rather than sending them to lkml which can take
>>>> long time.
>>> Yes, developing in your own sandbox can always be faster, but there is
>>> no feedback loop.
>> I was finding it real hard to find time to properly discuss each patch
>> over LKML, so I thought of shifting focus to local project repository
>> and then later go through proper reviews.
> So, should I delete the version in staging, or are you going to send
> patches to sync it up with your development version?
Deleting it from staging would not help much. Much more helpful would
be to sync at least the mainline and linux-next version of the driver
so it's easier to develop against these kernel trees. Initially, I
thought -staging means that any reviewed change can quickly make it
to *both* linux-next and more importantly -staging in mainline. Working/
Testing against mainline is much smoother than against linux-next.
More information about the devel