From: Jeff Garzik <jeff@garzik.org>
To: Mark Lord <liml@rtr.ca>
Cc: Tejun Heo <tj@kernel.org>,
IDE/ATA development list <linux-ide@vger.kernel.org>
Subject: Re: [PATCH #upstream-fixes 2/4] libata: beef up iterators
Date: Wed, 29 Oct 2008 21:58:24 -0400 [thread overview]
Message-ID: <490914C0.8050703@garzik.org> (raw)
In-Reply-To: <49090CFF.80101@rtr.ca>
Mark Lord wrote:
> Jeff Garzik wrote:
>> Tejun Heo wrote:
>>> There currently are the following loop constructs.
>>>
>>> * __ata_port_for_each_link() for all available links
>>> * ata_port_for_each_link() for edge links
>>> * ata_link_for_each_dev() for all devices
>>> * ata_link_for_each_dev_reverse() for all devices in reverse order
>>>
>>> Now there's a need for loop construct which is similar to
>>> __ata_port_for_each_link() but iterates over PMP links before the host
>>> link. Instead of adding another one with long name, do the following
>>> cleanup.
>>>
>>> * Implement and export ata_link_next() and ata_dev_next() which take
>>> @mode parameter and can be used to build custom loop.
>>> * Implement ata_for_each_link() and ata_for_each_dev() which take
>>> looping mode explicitly.
>>>
>>> The following iteration modes are implemented.
>>>
>>> * ATA_LITER_EDGE : loop over edge links
>>> * ATA_LITER_HOST_FIRST : loop over all links, host link first
>>> * ATA_LITER_PMP_FIRST : loop over all links, PMP links first
>>>
>>> * ATA_DITER_ENABLED : loop over enabled devices
>>> * ATA_DITER_ENABLED_REVERSE : loop over enabled devices in reverse
>>> order
>>> * ATA_DITER_ALL : loop over all devices
>>> * ATA_DITER_ALL_REVERSE : loop over all devices in reverse order
>>>
>>> This change removes exlicit device enabledness checks from many loops
>>> and makes it clear which ones are iterated over in which direction.
>>>
>>> Signed-off-by: Tejun Heo <tj@kernel.org>
>>> ---
>>> drivers/ata/ahci.c | 8 -
>>> drivers/ata/ata_generic.c | 5 -
>>> drivers/ata/libata-acpi.c | 19 +---
>>> drivers/ata/libata-core.c | 183
>>> ++++++++++++++++++++++++++++---------------
>>> drivers/ata/libata-eh.c | 84 ++++++++-----------
>>> drivers/ata/libata-pmp.c | 22 ++---
>>> drivers/ata/libata-scsi.c | 22 ++---
>>> drivers/ata/pata_it821x.c | 34 +++----
>>> drivers/ata/pata_ixp4xx_cf.c | 14 +--
>>> drivers/ata/pata_legacy.c | 17 +--
>>> drivers/ata/pata_pdc2027x.c | 27 ++----
>>> drivers/ata/pata_platform.c | 14 +--
>>> drivers/ata/pata_rz1000.c | 16 +--
>>> drivers/ata/sata_sil.c | 2 include/linux/libata.h
>>> | 50 +++++++----
>>> 15 files changed, 279 insertions(+), 238 deletions(-)
>>
>> ACK... for 2.6.29. I think this is too much change for -rc2. It's a
>> good idea though.
>>
>> Also, it could use more documentation than just the commit message...
>> something that programmers can easily refer to (header file comment?)
> ..
>
> Yeah. Especially a reminder of what "LITER" and "DITER" stand for! :)
Well, DITER stands for device iteration, and LITER stands for an amount
of petrol... <grin>
Jeff
next prev parent reply other threads:[~2008-10-30 1:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-26 6:50 [PATCH #upstream-fixes 1/4] libata: fix device iteration bugs Tejun Heo
2008-10-26 6:51 ` [PATCH #upstream-fixes 2/4] libata: beef up iterators Tejun Heo
2008-10-26 6:51 ` [PATCH #upstream-fixes 3/4] libata: when restoring SControl during detach do the PMP links first Tejun Heo
2008-10-26 6:52 ` [PATCH #upstream-fixes 4/4] libata: perform port detach in EH Tejun Heo
2008-10-28 4:02 ` Jeff Garzik
2008-10-26 14:31 ` [PATCH #upstream-fixes 2/4] libata: beef up iterators Elias Oltmanns
2008-10-27 9:06 ` Tejun Heo
2008-10-27 9:39 ` Elias Oltmanns
2008-10-27 10:17 ` Tejun Heo
2008-10-27 11:58 ` Elias Oltmanns
2008-10-28 4:01 ` Jeff Garzik
2008-10-30 1:25 ` Mark Lord
2008-10-30 1:58 ` Jeff Garzik [this message]
2008-10-26 10:47 ` [PATCH #upstream-fixes 1/4] libata: fix device iteration bugs Sergei Shtylyov
2008-10-27 9:07 ` Tejun Heo
2008-10-27 10:59 ` [PATCH #upstream-fixes 1/4 UPDATED] " Tejun Heo
2008-10-28 3:57 ` 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=490914C0.8050703@garzik.org \
--to=jeff@garzik.org \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=tj@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).