Re: zram/zsmalloc issues in very low memory conditions

[Stephen Barber]

I did get zswap working without a backing store, using Bob's patches
from http://thread.gmane.org/gmane.linux.kernel.mm/105627/focus=105642
applied to 3.11-rc6, The major issue we had with it was that i915
graphics buffers were getting corrupted somehow, which wasn't a
problem with zram on the same kernel version. I'm sure with a little
more investigation that problem could be fixed, though, and I don't
think there were any other major problems with it in our (admittedly
not very exhaustive) testing of those patches.

Hope that helps,
Steve Barber

On Thu, Oct 31, 2013 at 5:27 PM, Luigi Semenzato <semenzato@xxxxxxxxxx> wrote:
> [apologies for the previous HTML email]
>
> Hi Olav,
>
> I haven't personally done it.  Seth outlines the configuration in this thread:
>
> http://thread.gmane.org/gmane.linux.kernel.mm/105378/focus=105543
>
> Stephen, can you add more detail from your experience?
>
> Thanks!
>
>
> On Thu, Oct 31, 2013 at 4:34 PM, Olav Haugan <ohaugan@xxxxxxxxxxxxxx> wrote:
>> Hi Luigi,
>>
>> On 10/24/2013 6:12 PM, Luigi Semenzato wrote:
>>> On Thu, Oct 24, 2013 at 5:35 PM, Olav Haugan <ohaugan@xxxxxxxxxxxxxx> wrote:
>>>> Hi Bob, Luigi,
>>>>
>>>> On 10/23/2013 5:55 PM, Bob Liu wrote:
>>>>>
>>>>> On 10/24/2013 05:51 AM, Olav Haugan wrote:
>>>>
>>>>> By the way, could you take a try with zswap? Which can write pages to
>>>>> real swap device if compressed pool is full.
>>>>
>>>> zswap might not be feasible in all cases if you only have flash as
>>>> backing storage.
>>>
>>> Zswap can be configured to run without a backing storage.
>>>
>>
>> I was under the impression that zswap requires a backing storage. Can
>> you elaborate on how to configure zswap to not need a backing storage?
>>
>>
>> Olav Haugan
>>
>> --
>> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>> hosted by The Linux Foundation
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/