From: bert hubert <bert.hubert@netherlabs.nl>
To: Andi Kleen <ak@suse.de>
Cc: Hisham Kotry <hkotry@gmail.com>, netdev@vger.kernel.org
Subject: Re: skb diet
Date: Sun, 16 Apr 2006 13:43:58 +0200 [thread overview]
Message-ID: <20060416114358.GA12333@outpost.ds9a.nl> (raw)
In-Reply-To: <200604152122.01914.ak@suse.de>
On Sat, Apr 15, 2006 at 09:22:01PM +0200, Andi Kleen wrote:
> And optimizing for uncommon cases (not TCP) doesn't seem too useful.
There are servers that do tens of megabits of UDP these days (think VoIP, or
in my case, DNS), so it not that uncommon.
Bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://netherlabs.nl Open and Closed source services
next prev parent reply other threads:[~2006-04-16 11:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-15 11:17 skb diet Hisham Kotry
2006-04-15 19:22 ` Andi Kleen
2006-04-16 11:43 ` bert hubert [this message]
2006-04-16 12:56 ` Hisham Kotry
2006-04-16 15:16 ` Andi Kleen
2006-04-17 5:25 ` David S. Miller
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=20060416114358.GA12333@outpost.ds9a.nl \
--to=bert.hubert@netherlabs.nl \
--cc=ak@suse.de \
--cc=hkotry@gmail.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).