public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Pavel Machek <pavel@suse.cz>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ide-dev 3/5] generic Power Management for IDE devices
Date: Thu, 3 Feb 2005 14:34:29 +0100	[thread overview]
Message-ID: <58cb370e050203053421b571be@mail.gmail.com> (raw)
In-Reply-To: <1107332644.14782.115.camel@localhost.localdomain>

On Thu, 03 Feb 2005 10:03:00 +0000, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> On Maw, 2005-02-01 at 23:03, Bartlomiej Zolnierkiewicz wrote:
> > On Sat, 22 Jan 2005 19:41:24 +0100, Pavel Machek <pavel@suse.cz> wrote:
> > > Why do you need to have state-machine? During suspend we are running
> > > single-threaded, it should be okay to just do the calls directly.
> > >                                 Pavel
> >
> > If we are running single-threaded I also see no reason for state-machine.
> > Ben?
> 
> There may be outstanding I/O running at the time of the suspend. You
> want to keep everything nicely ordered. The state machine suspend code
> looks to me the right answer and is cleaner.

Outstanding I/Os won't be a problem - suspend will be done as one
request.  Anyway, state machine is not going away.

      reply	other threads:[~2005-02-03 13:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-21 23:05 [ide-dev 3/5] generic Power Management for IDE devices Bartlomiej Zolnierkiewicz
2005-01-22 18:41 ` Pavel Machek
2005-02-01 23:03   ` Bartlomiej Zolnierkiewicz
2005-02-01 23:24     ` Pavel Machek
2005-02-01 23:24     ` Benjamin Herrenschmidt
2005-02-01 23:29       ` Pavel Machek
2005-02-03 10:03     ` Alan Cox
2005-02-03 13:34       ` Bartlomiej Zolnierkiewicz [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=58cb370e050203053421b571be@mail.gmail.com \
    --to=bzolnier@gmail.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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