From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Grover <andrew.grover@intel.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
john.ronciak@intel.com, christopher.leech@intel.com
Subject: Re: [RFC] [PATCH 0/3] ioat: DMA engine support
Date: Wed, 23 Nov 2005 22:54:04 +0000 [thread overview]
Message-ID: <1132786445.13095.32.camel@localhost.localdomain> (raw)
In-Reply-To: <4384E7F2.2030508@pobox.com>
On Mer, 2005-11-23 at 17:06 -0500, Jeff Garzik wrote:
> Sample ideas: VM page pre-zeroing. ATA PIO data xfers (async copy to
> static buffer, to dramatically shorten length of kmap+irqsave time).
> Extremely large memcpy() calls.
ATA PIO copies are 512 bytes of memory per sector and that is usually
already in cache and on cache line boundaries. You won't even be able to
measure it done by the CPU. I can't see the I/O engine sync cost being
worth it.
Might just about help large transfers I guess but you don't do
multisector which is the only case you'd get perhaps 8K an I/O.
> Additionally, current IOAT is memory->memory. I would love to be able
> to convince Intel to add transforms and checksums,
Not just transforms but also masks and maybe even merges and textures
would be rather handy 8)
next prev parent reply other threads:[~2005-11-23 22:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-23 20:26 [RFC] [PATCH 0/3] ioat: DMA engine support Andrew Grover
2005-11-23 22:06 ` Jeff Garzik
2005-11-23 22:30 ` Andi Kleen
2005-11-23 23:02 ` Jeff Garzik
2005-11-24 0:05 ` Alan Cox
2005-11-23 23:36 ` Jeff Garzik
2005-11-24 0:17 ` Benjamin LaHaise
2005-11-24 0:50 ` David S. Miller
2005-11-24 6:50 ` Andi Kleen
2005-11-24 15:24 ` Avi Kivity
2005-11-24 15:29 ` Andi Kleen
2005-11-24 15:35 ` Avi Kivity
2005-11-24 15:37 ` Andi Kleen
2005-11-23 22:54 ` Alan Cox [this message]
2005-11-23 22:56 ` Jeff Garzik
2005-12-08 22:13 ` Kumar Gala
2005-12-08 22:23 ` Roland Dreier
2005-12-08 22:42 ` Alan Cox
2005-12-09 7:12 ` Evgeniy Polyakov
2005-11-23 22:45 ` Jeff Garzik
2005-12-02 17:06 ` Jon Mason
2005-11-23 22:53 ` Jeff Garzik
2005-11-23 23:02 ` Alan Cox
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=1132786445.13095.32.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--cc=christopher.leech@intel.com \
--cc=jgarzik@pobox.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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).