public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: nigel@nigel.suspend2.net
Cc: linux-pm@lists.osdl.org
Subject: Re: question on freeze and aio
Date: Fri, 9 Feb 2007 23:16:29 +0100	[thread overview]
Message-ID: <200702092316.30240.rjw@sisk.pl> (raw)
In-Reply-To: <1171058926.1484.74.camel@nigel.suspend2.net>

On Friday, 9 February 2007 23:08, Nigel Cunningham wrote:
> Hi.
> 
> On Fri, 2007-02-09 at 17:03 -0500, Alan Stern wrote:
> > On Sat, 10 Feb 2007, Nigel Cunningham wrote:
> > 
> > > Hi.
> > > 
> > > On Fri, 2007-02-09 at 17:04 +0100, Oliver Neukum wrote:
> > > > Hi,
> > > > 
> > > > can there be running aio requests if all tasks are frozen?
> > > 
> > > Since tasks are frozen, no new aio requests would be submitted. We do a
> > > sync to ssek to complete existing requests; I haven't looked to see
> > > whether that would need extending to flush aio as well, but don't think
> > > that would be the case. Given everyone else's silence, so far, you might
> > > be better to ask the author(s) of the aio code.
> > 
> > I believe Nigel is basically correct.  However sync will only flush aio 
> > for block devices.  Other types of aio will remain active.
> > 
> > aio callbacks are interrupt-driven and execute in a workqueue (see
> > fs/aio.c), and as far as I can tell that workqueue doesn't freeze.  
> > Unless some general facility freezes all workqueues...
> 
> Hmm. That applies to Raid, too? I've had some reports of raid i/o being
> caught in the BUG_ON() I have to catch I/O that shouldn't be happening,
> but haven't gotten around to looking at them yet.

Yes, I think it applies to RAID, but that's because md_thread has been made
PF_NOFREEZE explicitly, since we want to be able to save the image to an
md-based swap.

Pretty much everything that uses workqueues can do that, too.

Greetings,
Rafael


-- 
If you don't have the time to read,
you don't have the time or the tools to write.
		- Stephen King

  reply	other threads:[~2007-02-09 22:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 16:04 question on freeze and aio Oliver Neukum
2007-02-09 21:24 ` Rafael J. Wysocki
2007-02-09 21:29 ` Nigel Cunningham
2007-02-09 22:03   ` Alan Stern
2007-02-09 22:08     ` Nigel Cunningham
2007-02-09 22:16       ` Rafael J. Wysocki [this message]
2007-02-09 22:23       ` Alan Stern
2007-02-09 22:09     ` Rafael J. Wysocki
2007-02-13 10:18       ` Pavel Machek
2007-02-13 15:53         ` Rafael J. Wysocki
2007-02-14 21:44           ` Pavel Machek
2007-02-13 21:01         ` Alan Stern
2007-02-14 17:25           ` Randy Dunlap
2007-02-14 21:32             ` Rafael J. Wysocki
2007-02-14 21:28           ` Rafael J. Wysocki
2007-02-14 23:40             ` Rafael J. Wysocki
2007-02-13 10:17     ` Pavel Machek
2007-02-13 15:54       ` Rafael J. Wysocki
2007-02-13 10:16 ` Pavel Machek

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=200702092316.30240.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=linux-pm@lists.osdl.org \
    --cc=nigel@nigel.suspend2.net \
    /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