From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Jens Axboe <axboe@kernel.dk>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
gaowanlong@cn.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] zram/zsmalloc promotion
Date: Tue, 30 Oct 2012 19:16:18 -0700 [thread overview]
Message-ID: <20121031021618.GA1142@kroah.com> (raw)
In-Reply-To: <20121031020443.GP15767@bbox>
On Wed, Oct 31, 2012 at 11:04:43AM +0900, Minchan Kim wrote:
> Hi Greg,
>
> On Tue, Oct 30, 2012 at 06:42:09PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Oct 31, 2012 at 10:06:42AM +0900, Minchan Kim wrote:
> > > Thanks all,
> > >
> > > At last, everybody who contributes to zsmalloc want to put it under /lib.
> > >
> > > Greg,
> > > What should I do for promoting this dragging patchset?
> >
> > You need to get the -mm developers to agree that this is something that
> > is worth accepting. I have yet to see any compeling argument why this
>
> I'm one of mm developers. :)
> Yes. I hope Andrew have a time to take a look.
>
> > even needs to be in the kernel in the first place.
>
> Confused. what do you mean "this"? "zsmalloc" or "zram" or "both"?
> If you mean "zsmalloc", I guess there were some lengthy thread about
> "why we need a new another allocator". Unfortunately, I didn't follow it
> at that time. Nitin, Pekka, Could you point out that thread? or summarize
> the result.
>
> >
> > I'm not moving this anywhere until you get their acceptance.
>
> I understand you.
>
> It's one of problem in current mm mailing list.
> As you know, many mm guys works for server, not embedded so they don't have
> big interest about embedded feature so prioirty of the feature was always
> low. CMA proved it and next turn is zram. Even new-comer in mm is few so
> review bandwidth is always low, too. :(
>
> How can I poke them?
You just did. If they ignore this, wait a week, and resend.
Persistance is key.
good luck,
greg k-h
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nitin Gupta <ngupta@vflare.org>,
Konrad Rzeszutek Wilk <konrad@darnok.org>,
Seth Jennings <sjenning@linux.vnet.ibm.com>,
Jens Axboe <axboe@kernel.dk>,
Dan Magenheimer <dan.magenheimer@oracle.com>,
Pekka Enberg <penberg@cs.helsinki.fi>,
gaowanlong@cn.fujitsu.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v3 0/3] zram/zsmalloc promotion
Date: Tue, 30 Oct 2012 19:16:18 -0700 [thread overview]
Message-ID: <20121031021618.GA1142@kroah.com> (raw)
In-Reply-To: <20121031020443.GP15767@bbox>
On Wed, Oct 31, 2012 at 11:04:43AM +0900, Minchan Kim wrote:
> Hi Greg,
>
> On Tue, Oct 30, 2012 at 06:42:09PM -0700, Greg Kroah-Hartman wrote:
> > On Wed, Oct 31, 2012 at 10:06:42AM +0900, Minchan Kim wrote:
> > > Thanks all,
> > >
> > > At last, everybody who contributes to zsmalloc want to put it under /lib.
> > >
> > > Greg,
> > > What should I do for promoting this dragging patchset?
> >
> > You need to get the -mm developers to agree that this is something that
> > is worth accepting. I have yet to see any compeling argument why this
>
> I'm one of mm developers. :)
> Yes. I hope Andrew have a time to take a look.
>
> > even needs to be in the kernel in the first place.
>
> Confused. what do you mean "this"? "zsmalloc" or "zram" or "both"?
> If you mean "zsmalloc", I guess there were some lengthy thread about
> "why we need a new another allocator". Unfortunately, I didn't follow it
> at that time. Nitin, Pekka, Could you point out that thread? or summarize
> the result.
>
> >
> > I'm not moving this anywhere until you get their acceptance.
>
> I understand you.
>
> It's one of problem in current mm mailing list.
> As you know, many mm guys works for server, not embedded so they don't have
> big interest about embedded feature so prioirty of the feature was always
> low. CMA proved it and next turn is zram. Even new-comer in mm is few so
> review bandwidth is always low, too. :(
>
> How can I poke them?
You just did. If they ignore this, wait a week, and resend.
Persistance is key.
good luck,
greg k-h
next prev parent reply other threads:[~2012-10-31 2:15 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 8:56 [PATCH v3 0/3] zram/zsmalloc promotion Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 1/3] zsmalloc: promote to lib/ Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 2/3] zram: promote zram from staging Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 8:56 ` [PATCH v3 3/3] zram: select ZSMALLOC when ZRAM is configured Minchan Kim
2012-10-29 8:56 ` Minchan Kim
2012-10-29 15:43 ` [PATCH v3 0/3] zram/zsmalloc promotion Seth Jennings
2012-10-29 15:43 ` Seth Jennings
2012-10-31 1:06 ` Minchan Kim
2012-10-31 1:06 ` Minchan Kim
2012-10-31 1:42 ` Greg Kroah-Hartman
2012-10-31 1:42 ` Greg Kroah-Hartman
2012-10-31 2:04 ` Minchan Kim
2012-10-31 2:04 ` Minchan Kim
2012-10-31 2:16 ` Greg Kroah-Hartman [this message]
2012-10-31 2:16 ` Greg Kroah-Hartman
2012-10-31 2:39 ` Minchan Kim
2012-10-31 2:39 ` Minchan Kim
2012-10-31 2:43 ` Greg Kroah-Hartman
2012-10-31 2:43 ` Greg Kroah-Hartman
2012-10-31 7:02 ` Minchan Kim
2012-10-31 7:02 ` Minchan Kim
2012-10-31 16:19 ` Greg Kroah-Hartman
2012-10-31 16:19 ` Greg Kroah-Hartman
2012-11-01 2:45 ` Minchan Kim
2012-11-01 2:45 ` Minchan Kim
[not found] <<1351501009-15111-1-git-send-email-minchan@kernel.org>
2012-10-29 15:25 ` Dan Magenheimer
2012-10-29 15:25 ` Dan Magenheimer
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=20121031021618.GA1142@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--cc=dan.magenheimer@oracle.com \
--cc=gaowanlong@cn.fujitsu.com \
--cc=konrad@darnok.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=minchan@kernel.org \
--cc=ngupta@vflare.org \
--cc=penberg@cs.helsinki.fi \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.