From: Elias Oltmanns <eo@nebensachen.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
tj@kernel.org, jeff@garzik.org
Subject: Re: [PATCH 1/2] libata: get rid of ATA_MAX_QUEUE loop in ata_qc_complete_multiple()
Date: Wed, 22 Oct 2008 20:23:50 +0200 [thread overview]
Message-ID: <878wsgqyix.fsf@denkblock.local> (raw)
In-Reply-To: 1224661243-7929-2-git-send-email-jens.axboe@oracle.com
Jens Axboe <jens.axboe@oracle.com> wrote:
> We very rarely (if ever) complete more than one command in the
> sactive mask at the time, even for extremely high IO rates. So
> looping over the entire range of possible tags is pointless,
> instead use __ffs() to just find the completed tags directly.
>
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
> ---
> drivers/ata/libata-core.c | 15 +++++++++------
> 1 files changed, 9 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/ata/libata-core.c b/drivers/ata/libata-core.c
> index 1ee9499..c3c53e7 100644
> --- a/drivers/ata/libata-core.c
> +++ b/drivers/ata/libata-core.c
> @@ -4799,9 +4799,9 @@ void ata_qc_complete(struct ata_queued_cmd *qc)
> */
> int ata_qc_complete_multiple(struct ata_port *ap, u32 qc_active)
> {
> + unsigned int i = 0;
> int nr_done = 0;
> u32 done_mask;
> - int i;
>
> done_mask = ap->qc_active ^ qc_active;
>
> @@ -4811,16 +4811,19 @@ int ata_qc_complete_multiple(struct ata_port *ap, u32 qc_active)
> return -EINVAL;
> }
>
> - for (i = 0; i < ATA_MAX_QUEUE; i++) {
> + while (done_mask) {
> struct ata_queued_cmd *qc;
> + unsigned int next = __ffs(done_mask);
>
> - if (!(done_mask & (1 << i)))
> - continue;
> -
> - if ((qc = ata_qc_from_tag(ap, i))) {
> + qc = ata_qc_from_tag(ap, i + next);
> + if (qc) {
> ata_qc_complete(qc);
> nr_done++;
> }
> + if (++next >= ATA_MAX_QUEUE)
> + break;
If you think about it, this statement is equivalent to
if (ap->qc_active ^ qc_active == (1 << (ATA_MAX_QUEUE - 1)))
To fix this, you could say
if (++next + i >= ATA_MAX_QUEUE)
but perhaps it would be even more efficient (or not much worse) to skip
this check entirely.
Regards,
Elias
next prev parent reply other threads:[~2008-10-22 18:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-22 7:40 [PATCH 0/2] libata tag patches Jens Axboe
2008-10-22 7:40 ` [PATCH 1/2] libata: get rid of ATA_MAX_QUEUE loop in ata_qc_complete_multiple() Jens Axboe
2008-10-22 18:23 ` Elias Oltmanns [this message]
2008-10-23 8:23 ` Jens Axboe
2008-10-23 4:14 ` Tejun Heo
2008-10-23 6:37 ` Jens Axboe
2008-10-23 6:43 ` Jens Axboe
2008-10-23 13:40 ` Jens Axboe
2008-10-23 15:19 ` Elias Oltmanns
2008-10-24 8:14 ` Jens Axboe
2008-10-22 7:40 ` [PATCH 2/2] libata: switch to using block layer tagging support Jens Axboe
2008-10-23 0:46 ` Jeff Garzik
2008-10-23 6:33 ` Jens Axboe
2008-10-23 3:41 ` Tejun Heo
2008-10-24 7:08 ` Paul Mundt
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=878wsgqyix.fsf@denkblock.local \
--to=eo@nebensachen.de \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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 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.