From: Stewart Smith <stewart@flamingspork.com>
To: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [RFC] remove filestreams support?
Date: Tue, 05 Jul 2011 11:17:46 +1000 [thread overview]
Message-ID: <87sjqlbk5h.fsf@flamingspork.com> (raw)
In-Reply-To: <20110704153443.GA21501@infradead.org>
On Mon, 4 Jul 2011 11:34:43 -0400, Christoph Hellwig <hch@infradead.org> wrote:
> I'd like to know if there are any people actively using the filestreams
> support in XFS (-o filestreams). It's pretty much a fringe feature, and
> I've not seen any user reports for it, while it never passes all its
> XFSQA tests reliably. It was added specificly for CXFS media streaming
> operations on one particular array model that hasn't been sold for a
> long time. The feature purely is an in-memory one so unlike for example
> the realtime device there are no issue about beeing able to read old
> filesystems. The filestreams specific files are around 1500 lines of
> code, not even counting the hooks in the core XFS codebase.
I used it a bit on MythTV box to help circumvent the stupid behaviour of
it fsync()ing every second[1] leading to poor file layout on disk. I
found that filestreams worked a bit better than just setting allocsize
mount option... but I wouldn't be screaming too much if it went away....
[1] which was to work around ext3 taking locks for so long that you'd
then miss part of your TV program
--
Stewart Smith
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-05 1:17 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 [this message]
2011-07-05 1:54 ` Dave Chinner
2011-07-05 11:01 ` Christoph Hellwig
2011-07-08 21:07 ` Alex Elder
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=87sjqlbk5h.fsf@flamingspork.com \
--to=stewart@flamingspork.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