Let's get a File & Storage miniconf going at LPC2015!

Let's get a File & Storage miniconf going at LPC2015!

[Darrick J. Wong]

Hi again,

Early registration for this summer's Plumbers in Seattle, Washington ends
next Friday the 22nd.  With that in mind, I still don't have quite enough
people listed on the File & Storage miniconf wiki page for the organizers
to declare us an official miniconference, so if you're planning to go, or
even think you might go, please take a look at the planning page[1] and
add your name!

At a bare minimum, it seems like we can continue the ongoing discussions
around SMR exploration; the work going on with persistent memory and how to
expose it to filesystems and user apps; I see a proposal for the refereed
talks about the ongoing Open SSD work; and there have been prompts for more
conversation about rich ACL integration and supporting RDMA in NFS and Samba.
I think it would also be a good place to talk more about how to better
accomodate userspace filesystems like Ceph, giving things like the recent
O_NOMTIME thread, and other things like copy_file_range().

We of course are not limited to just those topics -- if there's something
you'd really like to discuss with everyone, please add that to the wiki.
I realize that mid-August is family vacation time for many people, but
those are the constraints the conference has to work with this year.
There are fun things to do around Seattle, and that's probably the best
time of year to visit.

--Darrick

[1] http://wiki.linuxplumbersconf.org/2015:file_and_storage_systems

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

Re: Let's get a File & Storage miniconf going at LPC2015!

[Kent Overstreet]

On Fri, May 15, 2015 at 01:58:25PM -0700, Darrick J. Wong wrote:
> We of course are not limited to just those topics -- if there's something
> you'd really like to discuss with everyone, please add that to the wiki.
> I realize that mid-August is family vacation time for many people, but
> those are the constraints the conference has to work with this year.
> There are fun things to do around Seattle, and that's probably the best
> time of year to visit.

It's getting near time for the big bcachefs announcement :)

Also, stable pages - what's been going on there? Last I heard you were talking
about using the page migration code to do COW, did anything come of that? I just
added data checksumming/compression to bcachefs, so that's been fresh on my
mind.

Also, there's probably always going to be situations where we're reading or
writing to pages user space can stomp on (dio) - IMO we need to add a bio flag
to annotate this - "if you need this to be stable you have to bounce it".
Otherwise either filesystems/block drivers are going to be stuck bouncing
everything, or it'll just (continue to be) buggy.

Re: Let's get a File & Storage miniconf going at LPC2015!

[Darrick J. Wong]

On Tue, May 19, 2015 at 08:42:00AM -0700, Kent Overstreet wrote:
> On Fri, May 15, 2015 at 01:58:25PM -0700, Darrick J. Wong wrote:
> > We of course are not limited to just those topics -- if there's something
> > you'd really like to discuss with everyone, please add that to the wiki.
> > I realize that mid-August is family vacation time for many people, but
> > those are the constraints the conference has to work with this year.
> > There are fun things to do around Seattle, and that's probably the best
> > time of year to visit.
> 
> It's getting near time for the big bcachefs announcement :)
> 
> Also, stable pages - what's been going on there? Last I heard you were talking
> about using the page migration code to do COW, did anything come of that? I just
> added data checksumming/compression to bcachefs, so that's been fresh on my
> mind.

Yeah.  I never figured out a sane way to migrate pages and keep everything
else happy.  Daniel Phillips is having a go at page forking for tux3; let's
see if the questions about that get resolved.

> Also, there's probably always going to be situations where we're reading or
> writing to pages user space can stomp on (dio) - IMO we need to add a bio flag
> to annotate this - "if you need this to be stable you have to bounce it".
> Otherwise either filesystems/block drivers are going to be stuck bouncing
> everything, or it'll just (continue to be) buggy.

Well, for now there's BIO_SNAP_STABLE that forces the block layer to bounce it,
but right now ext3 is the last user of it, and afaict btrfs is the only other
FS that takes care of stable pages on its own.

--D

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs