netdev
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared

from [Christoph Hellwig] [Permanent Link][Original]
To: "Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx>
Subject: Re: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Thu, 29 Jul 2004 19:25:19 +0100
Cc: jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <468F3FDA28AA87429AD807992E22D07E01F23824@orsmsx408>; from ganesh.venkatesan@xxxxxxxxx on Thu, Jul 29, 2004 at 11:17:08AM -0700
References: <468F3FDA28AA87429AD807992E22D07E01F23824@orsmsx408>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i 
On Thu, Jul 29, 2004 at 11:17:08AM -0700, Venkatesan, Ganesh wrote:
> Vmalloc space is less scarce than kmalloc space. Am I right? This patch
> trades kmalloc space for vmalloc space.

No, it's not.  vmalloc needs virtual space that's rather limited (e.g. 64MB
on PAE x86) in addition to physical memory.  Unless you do really big
allocations stay away from vmalloc.
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  RE: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w, Venkatesan, Ganesh
Next by Date:  [PATCH 2.6] BIC tcp congestion calculation timestamp, Stephen Hemminger
Previous by Thread:  RE: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w, Venkatesan, Ganesh
Next by Thread:  Re: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w, Herbert Xu
Indexes:  [Date] [Thread] [Top] [All Lists]