linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jeff@garzik.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Tejun Heo <htejun@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Asynchronous scan support for libata
Date: Sat, 08 Sep 2007 13:34:44 -0400	[thread overview]
Message-ID: <46E2DD34.8000404@garzik.org> (raw)
In-Reply-To: <20070908171917.GC6809@parisc-linux.org>

Matthew Wilcox wrote:
> Can you tell me a bit more about these drivers?  Would it be possible to
> convert them to one host/many channels, which would give us the exclusion
> we want?


As a tangent, I would prefer a more "natural" representation than 
current, where there is a 1-1 correspondence between scsi_host and ATA 
controller instance, and a 1-1 correspondence between SCSI channels and 
ATA ports.

Alas _any_ change to the current setup requires special attention, 
because it is tied intimately into master/slave exclusion and scheduling.

I occasionally ponder what it would take to create an intelligent 
request scheduling framework that takes into account inflexible hardware 
bottlenecks like simplex (one command per controller, $n ports, $m 
devices), master/slave (one command port, $m devices), NCQ ($n commands 
per port, $m devices), port multipliers with their own bottlenecks, etc.

I see a lot of common code patterns in this area, but we are all sorta 
doing our own thing at a low level in drivers, because of subtle (and 
not-so-subtle) differences in hardware queueing support.

	Jeff, thinking out loud



  reply	other threads:[~2007-09-08 17:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-06 21:05 [PATCH] Asynchronous scan support for libata Matthew Wilcox
2007-09-08  8:10 ` Tejun Heo
2007-09-08 17:19   ` Matthew Wilcox
2007-09-08 17:34     ` Jeff Garzik [this message]
2007-09-08 20:27       ` Tejun Heo
2007-09-08 17:40     ` Tejun Heo
2007-09-08 18:48     ` Alan Cox
2007-10-02 14:41 ` Jeff Garzik
2007-10-04 13:21   ` Matthew Wilcox

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=46E2DD34.8000404@garzik.org \
    --to=jeff@garzik.org \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=matthew@wil.cx \
    /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).