From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [RFC] remove filestreams support?
Date: Fri, 8 Jul 2011 16:07:39 -0500 [thread overview]
Message-ID: <1310159259.3024.63.camel@doink> (raw)
In-Reply-To: <20110705110127.GA27102@infradead.org>
On Tue, 2011-07-05 at 07:01 -0400, Christoph Hellwig wrote:
> On Tue, Jul 05, 2011 at 11:54:58AM +1000, Dave Chinner wrote:
> > So rather than deprecating the functionality, perhaps we should look
> > at implementing it through a simpler, more generic, better
> > integrated interface? That will increase the usefulness of the
> > functionality for a much wider audience than it has now, and also
> > provide the virt/blk throttling folk with exactly the "don't cross
> > the streams" functionality they suggest filesystems are unable to
> > support easily.....
>
> That does indeed sound simpler, and also more useful. Do the users
> who have chimed in here (and off list) think such a scheme would be
> useful for them?
We have customers that make good use of filestreams.
I don't think it matters whether they use CXFS or XFS,
it's a very useful allocation strategy, and an important
feature for certain applications. I like the idea of
generalizing it and/or improving its interface though.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-07-08 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 15:34 [RFC] remove filestreams support? Christoph Hellwig
2011-07-05 1:17 ` Stewart Smith
2011-07-05 1:54 ` Dave Chinner
2011-07-05 11:01 ` Christoph Hellwig
2011-07-08 21:07 ` Alex Elder [this message]
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=1310159259.3024.63.camel@doink \
--to=aelder@sgi.com \
--cc=hch@infradead.org \
--cc=xfs@oss.sgi.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