| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH 3/3] Add timeout feature |
| From: | Pavel Machek <pavel@xxxxxxx> |
| Date: | Mon, 7 Jul 2008 13:07:31 +0200 |
| Cc: | Takashi Sato <t-sato@xxxxxxxxxxxxx>, akpm@xxxxxxxxxxxxxxxxxxxx, viro@xxxxxxxxxxxxxxxxxx, "linux-ext4@xxxxxxxxxxxxxxx" <linux-ext4@xxxxxxxxxxxxxxx>, "xfs@xxxxxxxxxxx" <xfs@xxxxxxxxxxx>, "dm-devel@xxxxxxxxxx" <dm-devel@xxxxxxxxxx>, "linux-fsdevel@xxxxxxxxxxxxxxx" <linux-fsdevel@xxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, axboe@xxxxxxxxx, mtk.manpages@xxxxxxxxxxxxxx |
| In-reply-to: | <20080701081026.GB16691@infradead.org> |
| References: | <20080630212450t-sato@mail.jp.nec.com> <20080701081026.GB16691@infradead.org> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.5.9i |
Hi!
> I still disagree with this whole patch. There is not reason to let
> the freeze request timeout - an auto-unfreezing will only confuse the
> hell out of the caller. The only reason where the current XFS freeze
> call can hang and this would be theoretically useful is when the
What happens when someone dirties so much data that vm swaps out
whatever process that frozen the filesystem?
I though that was why the timeout was there...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
|
| Previous by Date: | Re: 12 Veliciraptors again w/x4 card (~1gbyte/sec aggregate read)!, Justin Piszcz |
|---|---|
| Next by Date: | Re: [PATCH 3/3] Add timeout feature, Dave Chinner |
| Previous by Thread: | Re: [dm-devel] Re: [PATCH 3/3] Add timeout feature, Eric Sandeen |
| Next by Thread: | Re: [PATCH 3/3] Add timeout feature, Dave Chinner |
| Indexes: | [Date] [Thread] [Top] [All Lists] |