public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Sat, 21 Aug 2004 12:32:09 +0200	[thread overview]
Message-ID: <20040821103208.GF6755@suse.de> (raw)
In-Reply-To: <200408191514.13022.bzolnier@elka.pw.edu.pl>

On Thu, Aug 19 2004, Bartlomiej Zolnierkiewicz wrote:
> > 2.6 breaks really really easily if you have any traffic on a device and
> > issue a hdparm (or similar) command to it. Things like set_using_dma()
> > and ide_set_xfer_rate() just stomp all over the drive regardless of what
> > it's doing right now.
> 
> Yep, known problem.

Something should be done about it, it's pretty critical imho.

> > I hacked something up for the SUSE kernel to fix this _almost_, it still
> > doesn't handle cases where you want to serialize across more than a
> > single channel. Not a common case, but I think there is such hardware
> > out there (which?).
> >
> > Clearly something needs to be done about this, it's extremely
> > frustrating not to be able to reliably turn on dma on a drive at all.
> > I'm just tossing this one out there to solve 99% of the case, I'd like
> > some input from you on what you feel we should do.
> 
> 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.

-- 
Jens Axboe


  parent reply	other threads:[~2004-08-21 10:32 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 [this message]
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
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=20040821103208.GF6755@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