From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Jan Kara <jack@suse.cz>,
James.Bottomley@HansenPartnership.com,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: LSF 2013 call for participation?
Date: Tue, 15 Jan 2013 15:11:27 -0800 [thread overview]
Message-ID: <20130115231127.GA6422@blackbox.djwong.org> (raw)
In-Reply-To: <yq1fw2dxaly.fsf@sermon.lab.mkp.net>
[adding linux-mm to cc...]
On Mon, Jan 07, 2013 at 10:43:05AM -0500, Martin K. Petersen wrote:
> >>>>> "Jan" == Jan Kara <jack@suse.cz> writes:
>
> Jan> Hi, I wanted to ask about this year's LSFMM summit - I didn't see
> Jan> any call for participation yet although previous years it was sent
> Jan> out before Christmas.
>
> Really? I always thought they went out in January. In any case we are
> getting the call rolling.
>
> And for those that want to plan ahead the dates are April 18th and 19th
> in San Francisco. This year we're trailing the Collab Summit instead of
> preceding it:
>
> https://events.linuxfoundation.org/events/lsfmm-summit
There are a few things I'd like to hold a discussion about...
- How do we get from bcache/flashcache/dm-cache/enhanceio to a single upstream
driver? If we merge one of them, then can we cherry-pick the more easily
pluggable pieces of each into whatever gets merged? Which one would we
merge as a basis for the others?
- Stable pages part 3: Modifying existing block devices. A number of block
devices and filesystems provide their own page snapshotting, or play tricks
with the page bits to satisfy their own stability requirements. Can we
eliminate this?
Also, miscellaneous other odd topics:
- How many of the infrequently-tested mount options in ext4/others can we get
away with eliminating? Or at least hiding them behind a "pleaseeatmydata"
mount flag to minimize (hopefully) the amount of accidental data loss due to
wild mount incantations?
- Update on exposing T10/DIF data to userspace via the preadv/pwritev aio
interface. I ought to publish some code first.
- A discussion of deduplication could be fun, though I'm not sure its memory
and processing requirements make it a great candidate for kernel code, or
even general usage. I'm not even sure there's a practical way to, say, have
a userspace dedupe tool that could listen for delayed allocations and try to
suggest adjustments before commit time.
--D
>
> --
> Martin K. Petersen Oracle Linux Engineering
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
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 prev parent reply other threads:[~2013-01-15 23:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 12:37 LSF 2013 call for participation? Jan Kara
2013-01-07 15:43 ` Martin K. Petersen
2013-01-07 18:53 ` Jan Kara
2013-01-15 23:11 ` Darrick J. Wong [this message]
2013-01-16 10:41 ` Jan Kara
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=20130115231127.GA6422@blackbox.djwong.org \
--to=darrick.wong@oracle.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=martin.petersen@oracle.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).