From: Shannon Nelson <shannon.nelson@intel.com>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: davem@davemloft.net, jeff@garzik.org, dan.j.williams@intel.com,
christopher.leech@intel.com, peter.p.waskiewicz.jr@intel.com
Subject: [PATCH 0/7] I/OAT: Add support for DCA - Direct Cache Access
Date: Thu, 19 Jul 2007 17:44:34 -0700 [thread overview]
Message-ID: <20070720004403.13564.14294.stgit@localhost.localdomain> (raw)
The following series implements support for providers and clients of
Direct Cache Access (DCA), a method for warming the cache in the correct
CPU before needing data.
This series applies on GIT commit 5bae7ac9feba925fd0099057f6b23d7be80b7b41
ioat-new-device-ids.patch
- add devices id's for newer Intel chipsets which support DMA and DCA
ioat-rename-source-file.patch
- prepare for adding new functionality
ioat-dma-cleanups.patch
- cleanup some code ugliness
ioat-split-startup-code.patch
- split the DMA support code from the PCI startup
ioat-add-msi-msix-support.patch
- add support for various interrupt handling schemes
ioat-add-dca-support.patch
- add the dca driver
ioat-add-ioat-dca.patch
- add DCA services to the ioatdma driver
Please pull from my git tree at
git://lost.foo-projects.org/~sln/linux-2.6 dca-upstream
Thanks to Dan Williams, Auke Kok, PJ Waskiewicz, and Chris Leech for their
help.
sln
--
======================================================================
Mr. Shannon Nelson LAN Access Division, Intel Corp.
Shannon.Nelson@intel.com I don't speak for Intel
(503) 712-7659 Parents can't afford to be squeamish.
next reply other threads:[~2007-07-20 0:45 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 0:44 Shannon Nelson [this message]
2007-07-20 0:44 ` [PATCH 1/7] I/OAT: New device ids Shannon Nelson
2007-07-20 0:49 ` David Miller
2007-07-20 0:44 ` [PATCH 2/7] I/OAT: Rename the source file Shannon Nelson
2007-07-20 0:49 ` David Miller
2007-07-20 0:45 ` [PATCH 3/7] I/OAT: code cleanup from checkpatch output Shannon Nelson
2007-07-20 0:49 ` David Miller
2007-07-20 0:45 ` [PATCH 4/7] I/OAT: Split PCI startup from DMA handling code Shannon Nelson
2007-07-20 0:50 ` David Miller
2007-07-20 10:53 ` Andrey Panin
2007-07-20 16:33 ` Nelson, Shannon
2007-07-20 0:45 ` [PATCH 5/7] I/OAT: Add support for MSI and MSI-X Shannon Nelson
2007-07-20 0:51 ` David Miller
2007-07-20 17:43 ` Roland Dreier
2007-07-20 18:09 ` Waskiewicz Jr, Peter P
2007-07-20 19:05 ` Roland Dreier
2007-07-20 19:19 ` Waskiewicz Jr, Peter P
2007-07-20 19:49 ` Roland Dreier
2007-07-20 21:10 ` Leech, Christopher
2007-07-20 21:21 ` Roland Dreier
2007-07-20 21:32 ` Manu Abraham
2007-07-20 21:38 ` Roland Dreier
2007-07-20 21:49 ` Manu Abraham
2007-07-20 21:54 ` Nelson, Shannon
2007-07-20 21:59 ` Manu Abraham
2007-07-20 22:00 ` Nelson, Shannon
2007-07-20 22:07 ` Waskiewicz Jr, Peter P
2007-07-20 21:13 ` Nelson, Shannon
2007-07-20 0:45 ` [PATCH 6/7] DCA: Add Direct Cache Access driver Shannon Nelson
2007-07-20 0:52 ` David Miller
2007-07-20 16:35 ` Nelson, Shannon
2007-07-20 0:45 ` [PATCH 7/7] I/OAT: Add DCA services Shannon Nelson
2007-07-20 0:52 ` David Miller
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=20070720004403.13564.14294.stgit@localhost.localdomain \
--to=shannon.nelson@intel.com \
--cc=akpm@linux-foundation.org \
--cc=christopher.leech@intel.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
/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.