From: Jeff Garzik <jgarzik@pobox.com>
To: Mark Lord <liml@rtr.ca>
Cc: Tejun Heo <htejun@gmail.com>, Alan Cox <alan@redhat.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: Correct use of ap->lock versus ap->host->lock ?
Date: Thu, 06 Mar 2008 13:24:31 -0500 [thread overview]
Message-ID: <47D036DF.1050200@pobox.com> (raw)
In-Reply-To: <47D035D6.1060604@rtr.ca>
Mark Lord wrote:
> The big difference here, is that a single SATA controller in a system
> can have up to eight quasi-independent ports. So when we lock, we block
> activity on all 8 interfaces, rather than just the one we care about.
...hence the mention of multi-port NICs.
Jeff
next prev parent reply other threads:[~2008-03-06 18:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 15:48 Correct use of ap->lock versus ap->host->lock ? Mark Lord
2008-03-06 16:35 ` Jeff Garzik
2008-03-06 17:13 ` Mark Lord
2008-03-06 17:24 ` Mark Lord
2008-03-06 17:41 ` Jeff Garzik
2008-03-06 18:12 ` Jeff Garzik
2008-03-06 23:04 ` Tejun Heo
2008-03-06 17:28 ` Jeff Garzik
2008-03-06 17:36 ` Mark Lord
2008-03-06 17:57 ` Jeff Garzik
2008-03-06 18:20 ` Mark Lord
2008-03-06 18:24 ` Jeff Garzik [this message]
2008-03-07 11:47 ` Andi Kleen
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=47D036DF.1050200@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@redhat.com \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--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 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).