From: Christoph Hellwig <hch@infradead.org>
To: ganesh.venkatesan@intel.com
Cc: jgarzik@pobox.com, netdev@oss.sgi.com
Subject: Re: [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w
Date: Thu, 29 Jul 2004 18:50:26 +0100 [thread overview]
Message-ID: <20040729185026.A6033@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0407290726020.21929-100000@westville2.jf.intel.com>; from ganesh.venkatesan@intel.com on Thu, Jul 29, 2004 at 08:29:37AM -0700
This sounds rather bogus. vmallocspace is a scare ressource, don't use it
unless nessecary.
next prev parent reply other threads:[~2004-07-29 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-29 15:29 [PATCH 3/12 2.4] e1000 - use vmalloc for data structures not shared with h/w ganesh.venkatesan
2004-07-29 17:50 ` Christoph Hellwig [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-29 18:17 Venkatesan, Ganesh
2004-07-29 18:25 ` Christoph Hellwig
2004-07-31 7:38 ` Herbert Xu
2004-08-04 16:48 ` 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=20040729185026.A6033@infradead.org \
--to=hch@infradead.org \
--cc=ganesh.venkatesan@intel.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).