From: Mark Lord <lkml@rtr.ca>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] libata: rewrite SCSI host scheme to be one per ATA host
Date: Wed, 22 Apr 2009 09:09:09 -0400 [thread overview]
Message-ID: <49EF16F5.5080909@rtr.ca> (raw)
In-Reply-To: <20090422090929.GA14928@havoc.gtf.org>
Jeff Garzik wrote:
> Currently, libata creates a Scsi_Host per port. This was originally
> done to leverage SCSI's infrastructure to arbitrate among master/slave
> devices, but is not needed for most modern SATA controllers. And I
> _think_ it is not needed for master/slave if done properly, either.
>
> The patch below converts libata such that there is now a 1:1
> correspondence between struct Scsi_Host and struct ata_host. ATA ports
> are represented as SCSI layer 'channels', which is more natural.
>
> This patch is an experiment, and not meant for upstream anytime soon.
..
Could you perhaps explain how error handling would behave in this scheme?
Currently, one SATA port can have failures without any impact whatsoever
on concurrent operation of other ports, in part because each port is treated
as a completely independent SCSI host.
I wonder if that changes with the new (better) scheme proposed here?
next prev parent reply other threads:[~2009-04-22 13:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 9:09 [PATCH] libata: rewrite SCSI host scheme to be one per ATA host Jeff Garzik
2009-04-22 9:23 ` Jeff Garzik
2009-04-22 12:16 ` Boaz Harrosh
2009-04-22 15:10 ` Daniela Engert
2009-04-22 15:18 ` Alan Cox
2009-04-22 15:37 ` James Bottomley
2009-04-22 16:27 ` Alan Cox
2009-04-22 18:36 ` Jeff Garzik
2009-04-22 19:27 ` James Bottomley
2009-04-22 16:48 ` Jeff Garzik
2009-04-23 6:35 ` Jens Axboe
2009-04-23 10:39 ` Jeff Garzik
2009-04-23 10:43 ` Jens Axboe
2009-04-22 13:09 ` Mark Lord [this message]
2009-04-22 16:52 ` Jeff Garzik
2009-04-22 19:08 ` Grant Grundler
2009-04-23 11:00 ` Jeff Garzik
2009-04-23 17:59 ` Grant Grundler
2009-04-23 18:09 ` James Bottomley
2009-04-24 11:00 ` Stefan Richter
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=49EF16F5.5080909@rtr.ca \
--to=lkml@rtr.ca \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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).