public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Jens Axboe <axboe@suse.de>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: serialize access to ide device
Date: Thu, 19 Aug 2004 13:32:06 +0100	[thread overview]
Message-ID: <1092918716.28141.19.camel@localhost.localdomain> (raw)
In-Reply-To: <200408191514.13022.bzolnier@elka.pw.edu.pl>

On Iau, 2004-08-19 at 14:14, Bartlomiej Zolnierkiewicz 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?

Definitely the right direction but it doesn't ultimately fix the bigger
problem which is that in some cases you need to issue multiple commands
in order to set up the drive and cannot do that in one sequence if the
drive is active. This could also be done with some kind of ATA_IO SG_IO
like functionality for the most part (the drive side).

The reset() logic also has the same problem when it occurs from process
context. The newer 2.4 code in 2.6 as well is only a bandaid that
normally works.

Serialization is indeed needed for some controllers (CMD64x in some
cases, RZ1000 and others). Certain controllers have drive pair
constraints and in some cases BIOSes know a lot about DMA suitability of
their configurations. Thats more an argument that using hdparm -d1 at
random is playing with fire.

Alan


  reply	other threads:[~2004-08-19 13:34 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 [this message]
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
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=1092918716.28141.19.camel@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --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