[lkml]   [2004]   [Jun]   [17]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: PATCH: Further aacraid work
On Thu, Jun 17, 2004 at 08:53:36AM -0400, Salyzyn, Mark wrote:
> Ideally we would like to have a mechanism to know if the
> DMAable area is limited to a 32 bit address space in order to take
> advantage of the more efficient FIB utilization.

Yes, you're not the only people who want this. There was a brief
discussion about this a few weeks ago, but I don't think anything's been
implemented yet.

It's a hard problem. Where's the right tradeoff? I have a system that
has a memory map that puts the first 3.75GB of memory at 0, then the
next 256MB at 64GB, then continues from 4GB. If there's only 4GB of
RAM in that system, I'm sure you'd rather use 32-bit descriptors and
anything in that 256MB gets bounce-buffered.

But where's the line? Who gets to decide? Is this really per-arch,
or is it per-driver, or is it somewhere else?

"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 14:03    [W:0.034 / U:0.876 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site