linux-kernel - Re: [PATCH] xvmalloc: total

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 30 Dec 2011 10:21:58 +0530
From:	Ajeet Yadav <ajeet.yadav.77@...il.com>
To:	Nitin Gupta <ngupta@...are.org>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] xvmalloc: total_pages can be ulong

Hi Nitin,

I wish if I could somehow know your plans for next release, so that I
can schedule my work accordingly, else my work on zram will be total
waste of my time making patches and your time replying and reviewing
it. Finally I have decided to delete my zram git.

Thanks and wishes for new year in advance.

On Thu, Dec 29, 2011 at 7:28 PM, Nitin Gupta <ngupta@...are.org> wrote:
> Hi Ajeet,
>
> On 12/28/2011 12:50 AM, Ajeet Yadav wrote:
>
>> From 4763266cb0077d1082d4a1ef941448e9b4eb55ca Mon Sep 17 00:00:00 2001
>> From: Ajeet Yadav <ajeet.yadav.77@...il.com>
>> Date: Wed, 28 Dec 2011 11:08:34 +0530
>> Subject: [PATCH] xvmalloc: total_pages can be ulong
>>
>> total_pages is u64, its too large value considering
>> that its in page unit on both 32-bit and 64-bit system
>> , therefore make it ulong.
>>
>> Having done that we can use normal ++ and -- operators
>> instead of stat_inc() and stat_dec(), therefore
>> remove these functions as well.
>>
>
>
> I'm soon going to send patches which replace xvmalloc with a new allocator.
>
> Thanks,
> Nitin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/