From: Arnd Bergmann <arnd.bergmann@de.ibm.com>
To: linuxppc-dev@ozlabs.org
Cc: Thomas Q Klein <tklein@de.ibm.com>,
Jan-Bernd Themann <themann@de.ibm.com>,
netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Christoph Raisch <RAISCH@de.ibm.com>,
Marcus Eder <meder@de.ibm.com>,
tklein@linux.ibm.com, abergman@de.ibm.com,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [2.6.19 PATCH 3/7] ehea: queue management
Date: Fri, 18 Aug 2006 18:16:51 +0200 [thread overview]
Message-ID: <200608181816.52079.arnd.bergmann@de.ibm.com> (raw)
In-Reply-To: <OFC184057C.C58732A2-ONC12571CE.004E5EF6-C12571CE.004ED1D4@de.ibm.com>
On Friday 18 August 2006 16:24, Christoph Raisch wrote:
> And as always in performance tuning... one size fits all unfortunately is
> not the correct answer.
Ah, good. What is the maximum sensible value that you came up with?
> Therefore we'll leave that open to the user as most other new ethernet
> driver did as well.
Sure. The interesting question is whether you want to allow users
to set it to a value that is no longer sensible to do with
__get_free_pages() and requires vmalloc().
Arnd <><
next prev parent reply other threads:[~2006-08-18 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 11:31 [2.6.19 PATCH 3/7] ehea: queue management Jan-Bernd Themann
2006-08-18 12:17 ` Arjan van de Ven
2006-08-18 13:25 ` Thomas Klein
2006-08-18 13:47 ` Arnd Bergmann
2006-08-18 14:24 ` Christoph Raisch
2006-08-18 16:16 ` Arnd Bergmann [this message]
2006-08-18 14:33 ` Jörn Engel
2006-08-18 14:40 ` Jörn Engel
-- strict thread matches above, loose matches on Subject: below --
2006-08-22 12:53 Jan-Bernd Themann
2006-08-22 14:01 ` Arnd Bergmann
2006-08-22 13:51 ` Jan-Bernd Themann
2006-08-23 8:57 Jan-Bernd Themann
2006-09-04 10:39 Jan-Bernd Themann
2006-09-06 13:32 Jan-Bernd Themann
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=200608181816.52079.arnd.bergmann@de.ibm.com \
--to=arnd.bergmann@de.ibm.com \
--cc=RAISCH@de.ibm.com \
--cc=abergman@de.ibm.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=meder@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=themann@de.ibm.com \
--cc=tklein@de.ibm.com \
--cc=tklein@linux.ibm.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).