| To: | Christoph Hellwig <hch@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Fri, 29 Oct 2004 13:02:47 -0400 |
| Cc: | "Venkatesan, Ganesh" <ganesh.venkatesan@xxxxxxxxx>, netdev <netdev@xxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxx>, William Lee Irwin III <wli@xxxxxxxxxxxxxx> |
| In-reply-to: | <20041029130817.GA12301@xxxxxxxxxxxxx> |
| References: | <468F3FDA28AA87429AD807992E22D07E0312853C@orsmsx408> <20041029130817.GA12301@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 |
Christoph Hellwig wrote: 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)..
However, kmalloc() has much lower per-call limits than vmalloc().
I'm interested to see a VM person weigh in on this...
Drivers are certainly allowed to use vmalloc.
Jeff
|
| Previous by Date: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures, Jon Mason |
|---|---|
| Next by Date: | Re: TCP Hang (or close to it): Windows XP -> Linux (w/tcp_bic), Sridhar Samudrala |
| Previous by Thread: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures, Jon Mason |
| Next by Thread: | Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures, William Lee Irwin III |
| Indexes: | [Date] [Thread] [Top] [All Lists] |