linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <hughd@google.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: lsf-pc@lists.linux-foundation.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org
Subject: Re: [LSF/MM ATTEND] persistent transparent large
Date: Tue, 28 Jan 2014 12:42:08 -0800 (PST)	[thread overview]
Message-ID: <alpine.LSU.2.11.1401281213490.1633@eggly.anvils> (raw)
In-Reply-To: <20140128193833.GD20939@parisc-linux.org>

On Tue, 28 Jan 2014, Matthew Wilcox wrote:
> On Thu, Jan 23, 2014 at 04:23:04AM -0800, Hugh Dickins wrote:
> > I'm eager to participate in this year's LSF/MM, but no topics of my
> > own to propose: I need to listen to what other people are suggesting.
> > 
> > Topics of most interest to me span mm and fs: persistent memory and
> > xip, transparent huge pagecache, large sectors, mm scalability.
> 
> I don't want to particularly pick on Hugh here; indeed, I know he won't
> take it personally which is why I've chosen to respoond to Hugh's message

Sure, your remarks are completely appropriate, and very well directed.

> rather than any of the others.  I'm rather annoyed at the huge disrepancy
> between the number of people who are *saying* they're interested in
> persistent memory and the number of people who are reviewing patches
> relating to persistent memory.

It's fair enough, though, for people to express an interest in a topic,
without having time to contribute to it beforehand.  That does not earn
anyone a place, but may help the committee to choose between topics.

Frustrating for you, though; and for everyone else pushing a patchset.

> 
> As far as I'm concerned, the only people who have "earned" their way into
> attending the Summit based on contributing to persistent memory work
> would be Dave Chinner (er ... on the ctte already), Ted Ts'o (ditto),
> Jan Kara (ditto), Kirill Shutemov, Dave Hansen (who's not looking to
> attend this year), Ross Zwisler (ditto), and Andreas Dilger.

It might be a good idea to insist on significant review contributions
in relevant areas as a condition for attendance.  That's a matter for
the committee to decide (I expect it's already taken into account),
but it should help to improve our review rate.

Counts me out, but that's okay.

> 
> I'd particularly like a VM person to review these two patches:
> 
> http://marc.info/?l=linux-fsdevel&m=138983598101510&w=2
> http://marc.info/?l=linux-fsdevel&m=138983600001513&w=2

I'd love to give you a constructive answer, but I'm not going to
comment on 2 out of 22 without getting to grips with the 22.  You've
been thinking about this stuff for months: others need time too,
and this is far from the only patchset on their queues.

Hugh

--
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>

  reply	other threads:[~2014-01-28 20:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23 12:23 Hugh Dickins
2014-01-28 19:38 ` Matthew Wilcox
2014-01-28 20:42   ` Hugh Dickins [this message]
2014-01-29  1:52     ` Matthew Wilcox
2014-01-28 21:04   ` [Lsf-pc] " James Bottomley
2014-01-28 22:24     ` Hugh Dickins
2014-01-29  2:39     ` Matthew Wilcox
2014-01-29 23:00       ` James Bottomley

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=alpine.LSU.2.11.1401281213490.1633@eggly.anvils \
    --to=hughd@google.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lsf-pc@lists.linux-foundation.org \
    --cc=matthew@wil.cx \
    /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