All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>,
	netdev <netdev@oss.sgi.com>, Andrew Morton <akpm@osdl.org>,
	William Lee Irwin III <wli@holomorphy.com>
Subject: Re: [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures
Date: Fri, 29 Oct 2004 13:02:47 -0400	[thread overview]
Message-ID: <418277B7.7000705@pobox.com> (raw)
In-Reply-To: <20041029130817.GA12301@infradead.org>

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

  parent reply	other threads:[~2004-10-29 17:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-29 12:50 [PATCH netdev-2.6 7/10] ixgb: Replace kmalloc with vmalloc to allocate driver local data structures Venkatesan, Ganesh
2004-10-29 13:08 ` Christoph Hellwig
2004-10-29 15:28   ` Jon Mason
2004-10-29 17:02   ` Jeff Garzik [this message]
2004-10-29 17:36     ` William Lee Irwin III
2004-10-29 18:26       ` Jeff Garzik
2004-10-29 18:29         ` William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
2004-10-29 15:35 Venkatesan, Ganesh
2004-10-29 16:41 ` Jon Mason
2004-10-29 12:11 Ganesh Venkatesan
2004-10-29 12:14 ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=418277B7.7000705@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=akpm@osdl.org \
    --cc=ganesh.venkatesan@intel.com \
    --cc=hch@infradead.org \
    --cc=netdev@oss.sgi.com \
    --cc=wli@holomorphy.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.