From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] XFS: Kill filestreams cache flush
Date: Sat, 2 Jan 2010 07:46:49 -0500 [thread overview]
Message-ID: <20100102124649.GA8004@infradead.org> (raw)
In-Reply-To: <20100102121203.GG13802@discord.disaster>
On Sat, Jan 02, 2010 at 11:12:03PM +1100, Dave Chinner wrote:
> Which means that sync destroys active filestreams associations and
> that seems more broken to me than anything an active reference will
> cause. I think just letting them time out is better than having them
> destroyed by external operations. I'm happy to leave it there if you
> want....
Just trying to understand what's going on here. If you think the new
behaviour is better and it doesn't cause any regressions in QA I'm fine
with it. Consider it:
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-01-02 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 2:38 [PATCH] XFS: Kill filestreams cache flush Dave Chinner
2010-01-02 11:53 ` Christoph Hellwig
2010-01-02 12:12 ` Dave Chinner
2010-01-02 12:46 ` Christoph Hellwig [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=20100102124649.GA8004@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.com \
--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