diff options
| author | Arjan van de Ven <arjan@linux.intel.com> | 2009-01-10 10:18:44 -0800 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-01-10 15:06:52 -0800 |
| commit | fa853a48413c2ca1a5dc6b539bf07cf8e7247f8e (patch) | |
| tree | 043212be5120dd4e422b0a04fd33900258b8108d | |
| parent | 886ad09fc83342aa1c5a02a0b6d3298b78a8067f (diff) | |
libata: only ports >= 0 need to synchronize
In a discussio with Jeff Garzik, he mentioned that the serialization
for the libata port probes only needs to be within the domain of a host.
This means that for the first port of each host (with ID 0), we don't
need to wait, so we can relax our serialization a little.
Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
| -rw-r--r-- | drivers/ata/libata-core.c | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c index f810078fafcc..71218d76d75e 100644 --- a/drivers/ata/libata-core.c +++ b/drivers/ata/libata-core.c @@ -5925,8 +5925,10 @@ static void async_port_probe(void *data, async_cookie_t cookie) * If we're not allowed to scan this host in parallel, * we need to wait until all previous scans have completed * before going further. + * Jeff Garzik says this is only within a controller, so we + * don't need to wait for port 0, only for later ports. */ - if (!(ap->host->flags & ATA_HOST_PARALLEL_SCAN)) + if (!(ap->host->flags & ATA_HOST_PARALLEL_SCAN) && ap->port_no != 0) async_synchronize_cookie(cookie); /* probe */ |