| To: | "Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures |
| From: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
| Date: | Fri, 29 Oct 2004 14:08:17 +0100 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, jgarzik@xxxxxxxxx, netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <468F3FDA28AA87429AD807992E22D07E0312853C@orsmsx408> |
| References: | <468F3FDA28AA87429AD807992E22D07E0312853C@orsmsx408> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
On Fri, Oct 29, 2004 at 05:50:45AM -0700, Venkatesan, Ganesh wrote: > This is a trade-off between space allocated via kmalloc and vmalloc. My > understanding is that kmalloc space is more limited than vmalloc. Is > this incorrect? Yes. kmalloc space is only limited by the amount of free memory you have in your system, vmalloc has very low absolute limits (down to 64MB in some configurations).. > With the original implementation that used kmalloc for all allocations > in the driver, I have noticed allocation failures when the ring sizes > were set to 4096. 4096 what? |
| Previous by Date: | Re: [RFC] IPSEC failover and replay detection sequence numbers, jamal |
|---|---|
| Next by Date: | Re: [PATCH 7/6] cls_fw: CONFIG_NET_CLS_IND is not dependant on CONFIG_NET_CLS_ACT, jamal |
| Previous by Thread: | RE: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures, Venkatesan, Ganesh |
| Next by Thread: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures, Jon Mason |
| Indexes: | [Date] [Thread] [Top] [All Lists] |