[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120912023914.GA31715@bbox>
Date: Wed, 12 Sep 2012 11:39:14 +0900
From: Minchan Kim <minchan@...nel.org>
To: Jens Axboe <axboe@...nel.dk>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
Nitin Gupta <ngupta@...are.org>,
Seth Jennings <sjenning@...ux.vnet.ibm.com>,
Dan Magenheimer <dan.magenheimer@...cle.com>,
Konrad Rzeszutek Wilk <konrad@...nok.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Query of zram/zsmalloc promotion
Hi all,
I would like to promote zram/zsmalloc from staging tree.
I already tried it https://lkml.org/lkml/2012/8/8/37 but I didn't get
any response from you guys.
I think zram/zsmalloc's code qulity is good and they
are used for many embedded vendors for a long time.
So it's proper time to promote them.
The zram should put on under driver/block/. I think it's not
arguable but the issue is which directory we should keep *zsmalloc*.
Now Nitin want to keep it with zram so it would be in driver/blocks/zram/
But I don't like it because zsmalloc touches several fields of struct page
freely(and AFAIRC, Andrew had a same concern with me) so I want to put
it under mm/.
In addtion, now zcache use it, too so it's rather awkward if we put it
under dirver/blocks/zram/.
So questions.
To Andrew:
Is it okay to put it under mm/ ? Or /lib?
To Jens:
Is it okay to put zram under drvier/block/ If you are okay, I will start sending
patchset after I sort out zsmalloc's location issue.
--
Kind regards,
Minchan Kim
--
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