From: Minchan Kim <minchan@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Nitin Gupta <ngupta@vflare.org>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Konrad Rzeszutek Wilk <konrad@darnok.org>
Subject: Re: [PATCH v2] zsmalloc: Add Kconfig for enabling PTE method
Date: Wed, 6 Feb 2013 11:50:28 +0900 [thread overview]
Message-ID: <20130206025028.GH11197@blaptop> (raw)
In-Reply-To: <20130206022854.GA1681@kroah.com>
On Tue, Feb 05, 2013 at 06:28:54PM -0800, Greg Kroah-Hartman wrote:
> On Wed, Feb 06, 2013 at 11:17:08AM +0900, Minchan Kim wrote:
> > diff --git a/drivers/staging/zsmalloc/Kconfig b/drivers/staging/zsmalloc/Kconfig
> > index 9084565..232b3b6 100644
> > --- a/drivers/staging/zsmalloc/Kconfig
> > +++ b/drivers/staging/zsmalloc/Kconfig
> > @@ -8,3 +8,15 @@ config ZSMALLOC
> > non-standard allocator interface where a handle, not a pointer, is
> > returned by an alloc(). This handle must be mapped in order to
> > access the allocated space.
> > +
> > +config PGTABLE_MAPPING
> > + bool "Use page table mapping to access allocations that span two pages"
>
> No tabs?
>
> Please also put "ZSmalloc somewhere in the text here, otherwise it
> really doesn't make much sense when seeing it in a menu.
>
> > + depends on ZSMALLOC
> > + default n
>
> That's the default, so it can be dropped.
>
> > + help
> > + By default, zsmalloc uses a copy-based object mapping method to access
> > + allocations that span two pages. However, if a particular architecture
> > + performs VM mapping faster than copying, then you should select this.
> > + This causes zsmalloc to use page table mapping rather than copying
> > + for object mapping. You can check speed with zsmalloc benchmark[1].
> > + [1] https://github.com/spartacus06/zsmalloc
>
> Care to specify exactly _what_ architectures this should be set for or
> not? That will help the distros out a lot in determining if this should
> be enabled or not.
>
> > diff --git a/drivers/staging/zsmalloc/zsmalloc-main.c b/drivers/staging/zsmalloc/zsmalloc-main.c
> > index 06f73a9..2c1805c 100644
> > --- a/drivers/staging/zsmalloc/zsmalloc-main.c
> > +++ b/drivers/staging/zsmalloc/zsmalloc-main.c
> > @@ -207,6 +207,7 @@ struct zs_pool {
> > struct size_class size_class[ZS_SIZE_CLASSES];
> >
> > gfp_t flags; /* allocation flags used when growing pool */
> > +
> > };
> >
> > /*
>
> Why add this extra line?
>
> thanks,
>
> greg k-h
Sorry for bothering you.
I fixed all you pointed out.
Thanks for the review, Greg!
Here it goes.
------------------- 8< -------------------
next prev parent reply other threads:[~2013-02-06 2:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 2:17 [PATCH v2] zsmalloc: Add Kconfig for enabling PTE method Minchan Kim
2013-02-06 2:28 ` Greg Kroah-Hartman
2013-02-06 2:50 ` Minchan Kim [this message]
2013-02-06 16:47 ` Seth Jennings
2013-02-06 23:16 ` Minchan Kim
2013-02-17 6:19 ` Ric Mason
2013-02-18 18:07 ` Dan Magenheimer
2013-02-18 18:08 ` Seth Jennings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130206025028.GH11197@blaptop \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dan.magenheimer@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ngupta@vflare.org \
--cc=sjenning@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).