From: Arjan van de Ven <arjanv@redhat.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ganesh.venkatesan@intel.com
Subject: Re: [PATCH] e1000 - Use vmalloc for data structures not shared
Date: Mon, 23 Aug 2004 08:32:04 +0200 [thread overview]
Message-ID: <1093242724.2792.3.camel@laptop.fenrus.com> (raw)
In-Reply-To: <200408222225.i7MMPRNX019306@hera.kernel.org>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
On Thu, 2004-07-29 at 18:01, Linux Kernel Mailing List wrote:
> ChangeSet 1.1807.39.3, 2004/07/29 12:01:46-04:00, ganesh.venkatesan@intel.com
>
> [PATCH] e1000 - Use vmalloc for data structures not shared
eh why? You are aware that vmalloc'd datastructures are slower during
use (due to TLB overhead) right ?
These structures also don't look THAT big on first sight....
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next parent reply other threads:[~2004-08-23 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200408222225.i7MMPRNX019306@hera.kernel.org>
2004-08-23 6:32 ` Arjan van de Ven [this message]
2004-08-23 15:29 Daniel Blueman
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=1093242724.2792.3.camel@laptop.fenrus.com \
--to=arjanv@redhat.com \
--cc=ganesh.venkatesan@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®