From: Andi Kleen <andi@firstfloor.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: ak@linux.intel.com, konrad.wilk@oracle.com, akataria@vmware.com,
lenb@kernel.org, x86@kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, petr@vmware.com
Subject: Re: swiotlb detection should be memory hotplug aware ?
Date: Wed, 28 Jul 2010 13:09:57 +0200 [thread overview]
Message-ID: <8739v3kgl6.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100728190939D.fujita.tomonori@lab.ntt.co.jp> (FUJITA Tomonori's message of "Wed, 28 Jul 2010 19:10:19 +0900")
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> writes:
>
>> The other problem is that using only two bits for the needed address
>> space is also extremly
>> inefficient (4GB and 16MB on x86). Really want masks everywhere and
>> optimize for the
>> actual requirements.
>
> swiotlb doesn't allocate GFP_DMA memory. It handles only GFP_DMA32.
I was lumping GFP_DMA and swiotlb together here. The
pci_alloc_consistent() function uses both interchangedly.
They really effectively are the same thing these days
and just separated by historical accident.
> I have a half-baked patch for it. I'll send it later.
The problem are still the *_map users which usually cannot sleep,
and then it's difficult to grow.
For *_alloc it's relatively easy and to some extend already
implemented.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-07-28 11:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 2:07 swiotlb detection should be memory hotplug aware ? Alok Kataria
2010-03-13 3:09 ` Andi Kleen
2010-03-15 17:22 ` Alok Kataria
2010-03-16 0:51 ` [LKML] " Konrad Rzeszutek Wilk
2010-03-16 1:33 ` FUJITA Tomonori
2010-03-16 12:45 ` [LKML] " Konrad Rzeszutek Wilk
2010-03-17 22:48 ` Alok Kataria
2010-07-20 22:14 ` Alok Kataria
2010-07-21 4:58 ` FUJITA Tomonori
2010-07-21 17:13 ` Alok Kataria
2010-07-21 23:44 ` FUJITA Tomonori
2010-07-22 0:03 ` FUJITA Tomonori
2010-07-22 18:34 ` Alok Kataria
2010-07-23 14:22 ` Konrad Rzeszutek Wilk
2010-07-23 14:33 ` Andi Kleen
2010-07-23 14:59 ` Konrad Rzeszutek Wilk
2010-07-23 15:23 ` Andi Kleen
2010-07-28 10:10 ` FUJITA Tomonori
2010-07-28 11:09 ` Andi Kleen [this message]
2010-07-28 14:20 ` FUJITA Tomonori
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=8739v3kgl6.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=akataria@vmware.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=konrad.wilk@oracle.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vmware.com \
--cc=x86@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 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.