From: Jeff Garzik <jeff@garzik.org>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH 2/2] libata: switch to using block layer tagging support
Date: Wed, 22 Oct 2008 20:46:38 -0400 [thread overview]
Message-ID: <48FFC96E.5060604@garzik.org> (raw)
In-Reply-To: <1224661243-7929-3-git-send-email-jens.axboe@oracle.com>
Jens Axboe wrote:
> libata currently has a pretty dumb ATA_MAX_QUEUE loop for finding
> a free tag to use. Instead of fixing that up, convert libata to
> using block layer tagging - gets rid of code in libata, and is also
> much faster.
>
> Signed-off-by: Jens Axboe <jens.axboe@oracle.com>
> ---
> drivers/ata/libata-core.c | 66 ++++----------------------------------------
> drivers/ata/libata-scsi.c | 10 +++++-
> drivers/ata/libata.h | 19 +++++++++++-
> include/linux/libata.h | 1 -
> 4 files changed, 31 insertions(+), 65 deletions(-)
Just to be sure, I take it this patch series is for 2.6.29?
Seems nice to have, but since it wasn't ready for the merge window
opening...
Jeff
next prev parent reply other threads:[~2008-10-23 0:46 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
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 [this message]
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=48FFC96E.5060604@garzik.org \
--to=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.