From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Atanasov <alex@ssi.bg>
Cc: linux-kernel mailing list <linux-kernel@vger.kernel.org>,
Jens Axboe <axboe@suse.de>
Subject: Re: [RFC/PATCH] IDE Power Management try 1
Date: 25 Apr 2003 13:32:58 +0200 [thread overview]
Message-ID: <1051270378.15078.22.camel@gaston> (raw)
In-Reply-To: <3EA90176.2080304@ssi.bg>
> What about this - add __REQ_DRIVE_INTERNAL, and carry args in
> rq->cmd[16] [0] = PM, [1] = SUSPEND/RESUME, [2]= STATE ? IDE can use it
> for power managment, error handling (do not do it from interrupt
> context, but queue it), may be more. This way it would really makes
> things a bit better with the complicated IDE locking. SCSI and probably
> other block devices can benefit from this internal requests too, so the
> bit is not wasted.
I agree. IDE locking isn't _that_ complicated ;) Though currently, we do
handle requests right on interrupt completion so error handling wouldn't
be deferred by this trick.
Jens, what do you think ? You are the blkdev.h guy :)
Ben.
next prev parent reply other threads:[~2003-04-25 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-24 12:59 [RFC/PATCH] IDE Power Management try 1 Benjamin Herrenschmidt
2003-04-25 9:35 ` Alexander Atanasov
2003-04-25 10:33 ` Jens Axboe
2003-04-25 11:50 ` Benjamin Herrenschmidt
2003-04-25 12:04 ` Bartlomiej Zolnierkiewicz
2003-04-25 11:32 ` Benjamin Herrenschmidt [this message]
2003-04-25 11:49 ` Jens Axboe
2003-04-25 11:52 ` Benjamin Herrenschmidt
2003-04-25 11:57 ` Benjamin Herrenschmidt
2003-04-25 12:13 ` Bartlomiej Zolnierkiewicz
2003-04-25 12:47 ` Benjamin Herrenschmidt
2003-04-25 12:16 ` Bartlomiej Zolnierkiewicz
2003-04-25 12:47 ` Benjamin Herrenschmidt
2003-04-25 13:58 ` 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=1051270378.15078.22.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=alex@ssi.bg \
--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;
as well as URLs for NNTP newsgroup(s).