From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: [discuss] [1/3] Add 4GB DMA32 zone
Date: Mon, 12 Sep 2005 09:58:55 +0200 [thread overview]
Message-ID: <200509120958.55936.ak@suse.de> (raw)
In-Reply-To: <43254DF40200007800024E0D@emea1-mh.id2.novell.com>
On Monday 12 September 2005 09:44, Jan Beulich wrote:
> It seems a little strange to add individual zones one by one. I remember
> from an OS project I previously worked on that at some time our driver
> developers ran into one or more devices that were able to consume 31-bit
> physical addresses
That's likely the unnamed RAID controller with the broken firmware refered to
below (they might actually have fixed the firmware now) But for block
devices it's not really needed anyways. From my experience and those
of other folks (IA64) the 4GB zone + a small fallback zone is a good
compromise.
> (but not 32-bit ones, and don't ask me for details on
> what exact devices these were, I never knew). I thus wonder whether it
> wouldn't make more sense to generalize the logic and allow drivers to
> specify to the allocator how many physical address bits they can deal
> with.
Because that would likely either impact the page allocation fast path
by having unsuited data structures for the normal case or make the code to
allocate pages with arbitary boundaries really slow because the allocation
wouldn't be O(1). Didn't seem like a good tradeoff.
-Andi
next prev parent reply other threads:[~2005-09-12 7:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-11 16:59 [1/3] Add 4GB DMA32 zone Andi Kleen
2005-09-12 7:44 ` [discuss] " Jan Beulich
2005-09-12 7:58 ` Andi Kleen [this message]
2005-09-12 10:28 ` Alan Cox
2005-09-12 10:42 ` Andi Kleen
2005-09-12 11:33 ` Alan Cox
2005-09-12 11:22 ` Andi Kleen
2005-09-12 12:34 ` Alan Cox
2005-09-12 12:28 ` [discuss] " Andi Kleen
2005-09-12 18:18 ` Jeff Garzik
2005-09-12 22:02 ` Bart Hartgers
2005-09-13 3:20 ` Andi Kleen
2005-09-12 19:55 ` Mark Lord
2005-09-12 12:45 ` Roman Zippel
2005-09-12 12:46 ` Andi Kleen
2005-09-12 12:50 ` Roman Zippel
2005-09-12 12:54 ` Andi Kleen
2005-09-12 13:01 ` Roman Zippel
2005-09-13 9:15 ` Roman Zippel
2005-09-13 9:47 ` [discuss] " Andi Kleen
2005-09-13 10:15 ` Andrew Morton
2005-09-13 11:32 ` Andi Kleen
2005-09-13 12:09 ` Roman Zippel
2005-09-13 23:51 ` KAMEZAWA Hiroyuki
2005-10-03 15:46 ` Coywolf Qi Hunt
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=200509120958.55936.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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