On Thu, 26 Apr 2007, Lee Schermerhorn wrote:
> I have been considering an HP-platform-specific boot option [handled by
> a new ia64 machine vec op] to re-distance the interleaved node, but for
> other platforms, such as Kame's, I think we still need the ability to
> move the DMA zones last in the Normal zone lists. Or, exclude them
> altogether?
Maybe a solution would be to have a dma_penalty option on boot? The dma
penalty is added to the dma zone. If its higher than zero then the dma
zone will become a node at that distance to other nodes.
The default is zero which would leave it as is.
If you boot with
dma_penalty=40
then a new slit entry is generated for the DMA zone and its put at that
distance.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
