From: Nick Piggin <npiggin@suse.de>
To: linux-mm@kvack.org
Cc: lsf10-pc@lists.linuxfoundation.org
Subject: Linux Memory Management Summit 8-9 August
Date: Mon, 15 Feb 2010 16:22:23 +1100 [thread overview]
Message-ID: <20100215052222.GC5723@laptop> (raw)
There has not been a memory management specific event for several years,
so we are going to try an MM summit again this year. While they are
distinct events, we are leveraging the format and logistics of the
successful Linux Storage and Filesystems summit this year. There are
common interests on a technical level as well, so we do have the
possibility for joint sessions.
This year we'll hold the MM summit jointly with the Linux Storage and
Filesystems summit on the two days before LinuxCon in Boston (that's
Sunday and Monday) at the Renaissance Hotel:
http://events.linuxfoundation.org/events/linuxcon
We're planning to hold some sessions jointly and split into three tracks
(Filesystems, Storage and MM) for others, so we're encouraging proposals
for discussion that cover areas relevant to all three groups as well as
more specific technical topics.
Suggestions for agenda topics should be sent to
lsf10-pc@lists.linuxfoundation.org
and optionally cc the Linux list which would be most interested in it:
SCSI: linux-scsi@vger.kernel.org
FS: linux-fsdevel@vger.kernel.org (plus relevant fs specific list)
MM: linux-mm@kvack.org
Please tag your subject with [LSF/MM TOPIC] so those of us who're not
very organised can find them easily in our inboxes. The agenda topics
and attendees will be selected by the programme committee, but the final
agenda will be by formed by consensus of the attendees on the day.
We'll try to cap attendance at around 20 per track to facilitate
discussions although the final numbers will depend on the room sizes
at the venue.
Requests to attend should be sent to:
lsf10-pc@lists.linuxfoundation.org
please summarise what you'll bring to the meeting, and what you'd like
to discuss. please also tag your email with [ATTEND] so there's less
chance of it getting lost in the large mail pile.
Presentations are allowed to guide discussion, but are strongly
discouraged. There will be no recording or audio bridge, however
written minutes will be published as in previous years:
2009:
http://lwn.net/Articles/327601/
http://lwn.net/Articles/327740/
http://lwn.net/Articles/328347/
Prior years:
http://www.usenix.org/events/lsf08/tech/lsf08sums.pdf
http://www.usenix.org/publications/login/2007-06/openpdfs/lsf07sums.pdf
If you have feedback on last year's meeting that we can use to improve
this year's, please also send that to:
lsf10-pc@lists.linuxfoundation.org
Thanks,
Nick
--
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>
next reply other threads:[~2010-02-15 5:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 5:22 Nick Piggin [this message]
2010-02-15 5:39 ` Linux Memory Management Summit 8-9 August Nick Piggin
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=20100215052222.GC5723@laptop \
--to=npiggin@suse.de \
--cc=linux-mm@kvack.org \
--cc=lsf10-pc@lists.linuxfoundation.org \
/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).