From: Joerg Roedel <joro@8bytes.org>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Bjorn Helgaas <helgaas@kernel.org>,
christian.melki@t2data.com, linux-pci@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: Fwd: SWIOTLB on 32-bit PAE.
Date: Mon, 5 Oct 2015 12:00:52 +0200 [thread overview]
Message-ID: <20151005100051.GA12506@8bytes.org> (raw)
In-Reply-To: <20151003180007.GA4732@localhost.localdomain>
On Sat, Oct 03, 2015 at 02:00:19PM -0400, Konrad Rzeszutek Wilk wrote:
> Aye. I presume that you had done a small change already for this?
> Would you be willing to post it on lkml and CC me ?
Yes, I also think it is needed. SWIOTLB already correctly handles
buffers in HighMem, so enabling it for 32-bit PAE should be easy. Please
also CC me on the patch.
Joerg
prev parent reply other threads:[~2015-10-05 10:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <560E9007.1000604@t2data.com>
2015-10-02 14:20 ` Fwd: SWIOTLB on 32-bit PAE Christian Melki
2015-10-03 14:36 ` Bjorn Helgaas
2015-10-03 18:00 ` Konrad Rzeszutek Wilk
2015-10-05 10:00 ` Joerg Roedel [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=20151005100051.GA12506@8bytes.org \
--to=joro@8bytes.org \
--cc=christian.melki@t2data.com \
--cc=helgaas@kernel.org \
--cc=iommu@lists.linux-foundation.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-pci@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).