From: Jeff Garzik <jgarzik@pobox.com>
To: Tejun Heo <htejun@gmail.com>
Cc: Alan <alan@lxorguk.ukuu.org.uk>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: share PIO limits among devices sharing a channel
Date: Thu, 25 Jan 2007 07:44:47 -0500 [thread overview]
Message-ID: <45B8A63F.8060305@pobox.com> (raw)
In-Reply-To: <20070125123030.3093fb32@localhost.localdomain>
Alan wrote:
> On Thu, 25 Jan 2007 20:29:47 +0900
> Tejun Heo <htejun@gmail.com> wrote:
>
>> PIO xfermask limits should be shared by all devices on the same
>> channel to avoid violating device selection timing. libata used to
>
> NAK, this is totally wrong
>
>> + /* PIO xfermask limits are shared by all devices on the same
>> + * channel to avoid violating device selection timing.
>> + */
>> + for (i = 0; i < ATA_MAX_DEVICES; i++) {
>> + struct ata_device *d = &ap->device[i];
>> + unsigned int pio_mask;
>> +
>> + if (ata_dev_absent(d))
>> + continue;
>> +
>> + ata_unpack_xfermask(ata_id_xfermask(d->id),
>> + &pio_mask, NULL, NULL);
>> + pio_mask &= d->pio_mask;
>> + xfer_mask &= ata_pack_xfermask(pio_mask, UINT_MAX, UINT_MAX);
>> + }
>
> NAK
>
> This "guarantee" was deliberately removed long ago and is completely
> bogus.
>
> The good ATA chipsets do not suffer from selection timing limits of this
> form. The less smart ones do and the drivers correctly merge the timing
Agreed.
I'm curious what the motivation of this patch was?
Jeff
next prev parent reply other threads:[~2007-01-25 12:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-25 11:29 [PATCH] libata: share PIO limits among devices sharing a channel Tejun Heo
2007-01-25 12:30 ` Alan
2007-01-25 12:44 ` Jeff Garzik [this message]
2007-01-25 13:30 ` Tejun Heo
2007-01-25 13:50 ` Alan
2007-01-25 14:36 ` Tejun Heo
2007-01-25 14:25 ` Sergei Shtylyov
2007-01-25 14:51 ` Alan
2007-01-25 14:54 ` Sergei Shtylyov
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=45B8A63F.8060305@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=htejun@gmail.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.