From: "John W. Linville" <linville@tuxdriver.com>
To: linux-kernel@vger.kernel.org, discuss@x86-64.org,
linux-ia64@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Cc: ak@suse.de, tony.luck@intel.com, Asit.K.Mallick@intel.com,
gregkh@suse.de
Subject: [patch 2.6.14-rc2 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device}
Date: Wed, 28 Sep 2005 17:50:47 -0400 [thread overview]
Message-ID: <09282005175047.10096@bilbo.tuxdriver.com> (raw)
In-Reply-To: <12c511ca050926194784b63e5@mail.gmail.com>
Conduct some maintenance of the swiotlb code:
-- Move the code from arch/ia64/lib/ to lib/
-- Cleanup some cruft (code duplication)
-- Add support for syncing sub-ranges of mappings
-- Add support for syncing DMA_BIDIRECTIONAL mappings
-- Comment fixup & change record
Also, tack-on an x86_64 implementation of dma_sync_single_range_for_cpu
and dma_sync_single_range_for _device. This makes use of the new
swiotlb sync sub-range support.
In this (third) round, the new location for swiotlb is (again) lib/swiotlb.c.
This set does NOT include the PCI excision that Tony Luck started after the
last round of discussion.
Patches to follow...
next prev parent reply other threads:[~2005-09-28 21:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-26 22:08 [patch 2.6.14-rc2 0/5] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} Luck, Tony
2005-09-26 22:46 ` Grant Grundler
2005-09-27 0:14 ` John W. Linville
2005-09-27 2:47 ` Tony Luck
2005-09-28 21:50 ` John W. Linville [this message]
2005-09-28 21:50 ` [patch 2.6.14-rc2 1/6] swiotlb: move from arch/ia64/lib/ to lib/ John W. Linville
2005-09-28 21:50 ` [patch 2.6.14-rc2 2/6] swiotlb: cleanup some code duplication cruft John W. Linville
2005-09-28 21:50 ` [patch 2.6.14-rc2 3/6] swiotlb: support syncing sub-ranges of mappings John W. Linville
2005-09-28 21:50 ` [patch 2.6.14-rc2 4/6] swiotlb: support syncing DMA_BIDIRECTIONAL mappings John W. Linville
2005-09-28 21:50 ` [patch 2.6.14-rc2 5/6] swiotlb: file header comments John W. Linville
2005-09-28 21:50 ` [patch 2.6.14-rc2 6/6] x86_64: implement dma_sync_single_range_for_{cpu,device} John W. Linville
2005-09-29 22:42 ` [patch 2.6.14-rc2 0/6] swiotlb maintenance and x86_64 dma_sync_single_range_for_{cpu,device} Luck, Tony
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=09282005175047.10096@bilbo.tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Asit.K.Mallick@intel.com \
--cc=ak@suse.de \
--cc=discuss@x86-64.org \
--cc=gregkh@suse.de \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=tony.luck@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox