From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [RFC PATCH] libata: PIO via bounce buffer
Date: Sat, 1 Mar 2008 16:38:03 +0000 [thread overview]
Message-ID: <20080301163803.2ff1d1bc@core> (raw)
In-Reply-To: <47C8A2C0.7070005@garzik.org>
> Inside ata_bounce_pio_xfer(), get the buffer for your CPU. If NULL or
> too small, allocate new buffer, otherwise re-use existing buffer.
>
> This method makes the common case _not_ allocate anything, which should
> be obviously more efficient.
Obviously ?
kmalloc will usually return us a cache hot buffer very very fast. A
private allocator will return us an almost certainly cache cold buffer
slightly faster.
I'm not sure its that simple.
Alan
prev parent reply other threads:[~2008-03-01 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 13:51 [RFC PATCH] libata: PIO via bounce buffer Alan Cox
2008-03-01 0:26 ` Jeff Garzik
2008-03-01 16:38 ` Alan Cox [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=20080301163803.2ff1d1bc@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--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 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).