From: Jeff Garzik <jgarzik@pobox.com>
To: brking@us.ibm.com
Cc: linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [patch 08/15] libata: Add ability to prevent PRD from being allocated
Date: Thu, 09 Feb 2006 02:20:48 -0500 [thread overview]
Message-ID: <43EAED50.6060707@pobox.com> (raw)
In-Reply-To: <200602061542.k16FgXXX015889@d03av03.boulder.ibm.com>
brking@us.ibm.com wrote:
> For some HBAs, particularly SAS HBAs, there is no reason to
> allocate a PRD buffer, since it is not used. Add a flag
> to prevent its allocation.
>
> Signed-off-by: Brian King <brking@us.ibm.com>
ACK. This is nice to have regardless of SAS, and perhaps should be
bumped up in the patch order.
prev parent reply other threads:[~2006-02-09 7:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-06 15:42 [patch 08/15] libata: Add ability to prevent PRD from being allocated brking
2006-02-08 11:12 ` Tejun Heo
2006-02-08 14:28 ` Brian King
2006-02-09 9:22 ` Jeff Garzik
2006-02-09 7:20 ` Jeff Garzik [this message]
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=43EAED50.6060707@pobox.com \
--to=jgarzik@pobox.com \
--cc=brking@us.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@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 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).