From: Jens Axboe <axboe@suse.de>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: serialize access to ide device
Date: Mon, 23 Aug 2004 14:15:41 +0200 [thread overview]
Message-ID: <20040823121540.GN2301@suse.de> (raw)
In-Reply-To: <200408211913.47982.bzolnier@elka.pw.edu.pl>
On Sat, Aug 21 2004, Bartlomiej Zolnierkiewicz wrote:
> On Saturday 21 August 2004 18:21, Jens Axboe wrote:
> > On Sat, Aug 21 2004, Bartlomiej Zolnierkiewicz wrote:
> > > On Saturday 21 August 2004 12:32, Jens Axboe wrote:
> > > > > What about adding new kind of REQ_SPECIAL request and converting
> > > > > set_using_dma(), set_xfer_rate(), ..., to be callback functions for
> > > > > this request?
> > > > >
> > > > > This should be a lot cleaner and will cover 100% cases.
> > > >
> > > > That will still only serialize per-channel. But yes, a lot cleaner.
> > >
> > > per hwgroup not per channel
> > > (serializing per host device will be better but requires even more work)
> >
> > Sorry yes hwgroup, that's what I meant. The case I worried about in my
> > patch (and noted) is that it doesn't cover per-hwif and neither would a
> > special request.
>
> I guess you meant 'per-host' because hwif == channel.
>
> [ You are of course right for about 'per-host' case. ]
Yep, per host. So REQ_SPECIAL-like approach is cleaner, but doesn't
cover more cases than a simple hwif pinning would anyways. You'd need
some code to quisce the host in any case.
--
Jens Axboe
next prev parent reply other threads:[~2004-08-23 12:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 13:11 serialize access to ide device Jens Axboe
2004-08-02 13:41 ` Geert Uytterhoeven
2004-08-02 13:49 ` Jens Axboe
2004-08-19 13:14 ` Bartlomiej Zolnierkiewicz
2004-08-19 12:32 ` Alan Cox
2004-08-21 10:32 ` Jens Axboe
2004-08-21 14:43 ` Bartlomiej Zolnierkiewicz
2004-08-21 16:21 ` Jens Axboe
2004-08-21 17:13 ` Bartlomiej Zolnierkiewicz
2004-08-23 12:15 ` Jens Axboe [this message]
2004-08-23 15:02 ` Bartlomiej Zolnierkiewicz
2004-08-23 14:50 ` Alan Cox
2004-08-23 15:10 ` Jens Axboe
2004-08-23 16:07 ` Jeff Garzik
2004-08-23 16:59 ` 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=20040823121540.GN2301@suse.de \
--to=axboe@suse.de \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--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