[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BE50AA3.6040806@vflare.org>
Date: Sat, 08 May 2010 12:24:27 +0530
From: Nitin Gupta <ngupta@...are.org>
To: Pekka Enberg <penberg@...helsinki.fi>
CC: Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <greg@...ah.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Hugh Dickins <hugh.dickins@...cali.co.uk>,
Cyp <cyp561@...il.com>, Minchan Kim <minchan.kim@...il.com>,
Al Viro <viro@...IV.linux.org.uk>,
Christoph Hellwig <hch@...radead.org>,
Jens Axboe <jens.axboe@...cle.com>,
Andi Kleen <andi@...stfloor.org>,
driverdev <devel@...verdev.osuosl.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/3] ramzswap: Eliminate stale data from compressed memory
(v2)
Hi,
On 05/08/2010 11:59 AM, Pekka Enberg wrote:
>
> Andrew Morton wrote:
>> The driver appears to be controlled by some nasty-looking ioctl against
>> some fd. None of it is documented anywhere. It should be. You're
>> proposing here a permanent extension to the kernel ABI which we will
>> need to maintain for ever. That's a big deal and it is the very first
>> thing reviewers will look at, before even considering the code.
>
> I thought we got rid of it? Nitin?
>
No, we didn't get rid of any ioctls. In fact, issuing ioctls is how we
configure various ramzswap devices (using rzscontrol utility). The
functionality of all these ioctls is well documented in rzscontrol
manpage. Now, I will also add relevant comments in the code.
>> RZSIO_GET_STATS looks to be hopeless from a long-term maintainability
>> POV. It's debug code and it would be better to move it into a debugfs
>> file, where we can then add and remove things at will.
>
> Yup.
>
Its not debug code. This ioctl is how we send stats about given ramzswap
device to userspace: rzscontrol /dev/ramzswap --stats, invokes this ioctl
and prints the stats. I will add comments to this part to make it clear.
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/
Powered by blists - more mailing lists