From: Brian King <brking@us.ibm.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: [RFC 0/2] libata: support SATA devices on SAS HBAs
Date: Tue, 25 Oct 2005 12:57:23 -0500 [thread overview]
Message-ID: <435E7203.8020008@us.ibm.com> (raw)
In-Reply-To: <43443E99.4090008@pobox.com>
Jeff Garzik wrote:
> Bartlomiej Zolnierkiewicz wrote:
>
>>[PATCH] libata: add ops->qc_transport for SAS
>>
>>* add ->qc_transport to struct ata_port_operations
>>* add default ata_qc_transport() and update all host drivers
>>
>>Thanks to this change we won't have to depend on host_set
>>and host_set->lock for devices attached to SAS HBAs.
>>
>>Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
>
>
>
> Seems sane at a quick glance, though I'm a bit disappointed we have to
> add yet another level of indirection to the hot path.
>
> You made a good point, though, by pointing out that all the ata_qc_xxx
> stuff is essentially completely inside a single lock domain.
>
> Other notes: There may be other dependencies such as wanting to
> reference the struct device pointer in host_set and similar details that
> need handling. Also, I was planning to move some of the ata_port_ops
> into a separate host_set ops, since they (hooks such as ->irq_clear or
> ->host_stop) are really host-wide hooks, not per-port hooks.
Jeff,
Is this patch on its way into one of your trees, or should I just pick
it up add it to my libata SAS patchset so you can just grab the whole
patchset once it is ready?
Brian
--
Brian King
eServer Storage I/O
IBM Linux Technology Center
next prev parent reply other threads:[~2005-10-25 17:57 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 21:56 [RFC 0/2] libata: support SATA devices on SAS HBAs Brian King
2005-10-03 21:58 ` [RFC 1/2] libata: configurable host_set lock Brian King
2005-10-03 21:58 ` [RFC 2/2] libata: support SATA devices on SAS HBAs Brian King
2005-10-04 9:56 ` [RFC 0/2] " Jeff Garzik
2005-10-04 10:22 ` Bartlomiej Zolnierkiewicz
2005-10-04 20:56 ` Bartlomiej Zolnierkiewicz
2005-10-05 20:59 ` Jeff Garzik
2005-10-24 22:17 ` [PATCH " Brian King
2005-10-24 22:19 ` [PATCH 1/2] libata: Remove dependence on host_set->dev for SAS Brian King
2005-10-25 17:53 ` Jeff Garzik
2005-10-25 19:30 ` Brian King
2005-10-25 19:43 ` Jeff Garzik
2005-10-25 22:48 ` Luben Tuikov
2005-10-27 16:05 ` Brian King
2005-10-27 20:15 ` Luben Tuikov
2005-11-24 0:53 ` Douglas Gilbert
2005-11-24 1:07 ` Jeff Garzik
2005-11-24 8:12 ` Bartlomiej Zolnierkiewicz
2005-12-02 2:05 ` Jeff Garzik
2005-12-02 8:07 ` Bartlomiej Zolnierkiewicz
2005-12-02 10:28 ` Douglas Gilbert
2005-12-02 10:48 ` Jeff Garzik
2005-11-29 22:13 ` Brian King
2005-10-24 22:20 ` [PATCH 2/2] libata: Add support for SATA attachment to SAS adapters Brian King
2005-10-25 17:58 ` Jeff Garzik
2005-10-25 12:59 ` [PATCH 0/2] libata: support SATA devices on SAS HBAs Luben Tuikov
2005-10-25 13:39 ` Brian King
2005-10-25 13:40 ` Luben Tuikov
2005-10-25 13:53 ` Brian King
2005-10-25 14:08 ` Luben Tuikov
2005-10-25 14:27 ` Brian King
2005-10-25 17:51 ` Jeff Garzik
2005-10-25 17:57 ` Brian King [this message]
2005-10-25 18:07 ` [RFC " Jeff Garzik
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=435E7203.8020008@us.ibm.com \
--to=brking@us.ibm.com \
--cc=bzolnier@gmail.com \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.