From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Jens Axboe <axboe@suse.de>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] IDE Power Management, try 2
Date: 05 Jun 2003 16:30:43 +0200 [thread overview]
Message-ID: <1054823443.766.17.camel@gaston> (raw)
In-Reply-To: <1054823279.765.14.camel@gaston>
On Thu, 2003-06-05 at 16:27, Benjamin Herrenschmidt wrote:
> > > I had to add yet another rq->flags bit for that, and I think that sucks
> >
> > You don't have if you use additional, default pm_state (on == 0).
> > This sucks too, but a bit less.
>
> Can you elaborate ? I'm not sure I understand what you meant
Forget it, my brain finally got a clue ;) Though I don't like the
solution. Adding pm_step & pm_state to struct request or a ptr to
rq_pm_struct seem the way to go to me, though I'm not sure which
of these 2 solution is the best, struct request is already a can
of worms imho... ;) If we ever need more PM fields in there, then
the pointer may be the best solution, but right know, I can't think
of any reason to add more stuffs
> > I think extending struct request is the way to go,
> > pm_step & pm_state or even pointer to rq_pm_struct.
>
> Ok. I'll wait for Jens ack and go that way if he agrees.
>
> Ben.
--
Benjamin Herrenschmidt <benh@kernel.crashing.org>
next prev parent reply other threads:[~2003-06-05 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-05 13:46 [PATCH] IDE Power Management, try 2 Benjamin Herrenschmidt
2003-06-05 14:16 ` Bartlomiej Zolnierkiewicz
2003-06-05 14:27 ` Benjamin Herrenschmidt
2003-06-05 14:30 ` Benjamin Herrenschmidt [this message]
2003-06-06 4:35 ` Jens Axboe
2003-06-07 1:55 ` Andre Hedrick
2003-06-10 16:15 ` Jens Axboe
2003-06-10 16:27 ` Benjamin Herrenschmidt
2003-06-10 16:36 ` Bartlomiej Zolnierkiewicz
2003-06-10 16:58 ` Benjamin Herrenschmidt
2003-06-10 17:28 ` Jens Axboe
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=1054823443.766.17.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
/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