[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
[dm-devel] Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- From: David Chinner <dgc sgi com>
- To: "Rafael J. Wysocki" <rjw sisk pl>
- Cc: Andrew Morton <akpm osdl org>, Eric Sandeen <sandeen redhat com>, Nigel Cunningham <nigel suspend2 net>, David Chinner <dgc sgi com>, linux-kernel vger kernel org, dm-devel redhat com, Srinivasa DS <srinivasa in ibm com>, Pavel Machek <pavel ucw cz>, Alasdair G Kergon <agk redhat com>
- Subject: [dm-devel] Re: [PATCH 2.6.19 5/5] fs: freeze_bdev with semaphore not mutex
- Date: Fri, 10 Nov 2006 11:57:49 +1100
On Thu, Nov 09, 2006 at 11:21:46PM +0100, Rafael J. Wysocki wrote:
> I think we can add a flag to __create_workqueue() that will indicate if
> this one is to be running with PF_NOFREEZE and a corresponding macro like
> create_freezable_workqueue() to be used wherever we want the worker thread
> to freeze (in which case it should be calling try_to_freeze() somewhere).
> Then, we can teach filesystems to use this macro instead of
> create_workqueue().
At what point does the workqueue get frozen? i.e. how does this
guarantee an unfrozen filesystem will end up in a consistent
state?
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]