On 5/17/05, Andrew Morton <[email protected]> wrote: > I think the e1000 driver is being a bit insane there. I figure that Do you mean insane to use vmalloc? > sizeof(struct e1000_buffer) is 28 on 64-bit, so even with 4k pagesize we'll > always succeed in being able to support a 32k/32 = 1024-entry Tx ring. > > Is there any real-world reason for wanting larger ring sizes than that? > > We have had cases where allocation of 32K of memory (via kmalloc) fails. ganesh. - 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/
- Follow-Ups:
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Andrew Morton <[email protected]>
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- References:
- [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Christoph Lameter <[email protected]>
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Andrew Morton <[email protected]>
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Christoph Lameter <[email protected]>
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Christoph Lameter <[email protected]>
- Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- From: Andrew Morton <[email protected]>
- [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- Prev by Date: Re: Linux support for SiLabs CP210x devices
- Next by Date: Re: sparse error: unable to open 'stdarg.h'
- Previous by thread: Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- Next by thread: Re: [PATCH] NUMA aware allocation of transmit and receive buffers for e1000
- Index(es):
 |