From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, lgrijincu@ixiacom.com, opurdila@ixiacom.com
Subject: Re: [PATCH 0/8 net-next-2.6] udp: optimisations
Date: Sun, 08 Nov 2009 20:55:22 -0800 (PST) [thread overview]
Message-ID: <20091108.205522.185944441.davem@davemloft.net> (raw)
In-Reply-To: <4AF72738.7020606@gmail.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Sun, 08 Nov 2009 21:16:56 +0100
> This patch series address UDP scalability problems, we failed to solve in 2007
> (commit 6aaf47fa48d3c44 INET : IPV4 UDP lookups converted to a 2 pass algo)
> we had to revert a bit later.
Looks great, all applied, thanks Eric.
I would even go so far as to say that the cutoff to the second hash
table should be even lower than 10, like maybe 4 or 5.
next prev parent reply other threads:[~2009-11-09 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-08 20:16 [PATCH 0/8 net-next-2.6] udp: optimisations Eric Dumazet
2009-11-09 4:55 ` David Miller [this message]
2009-11-09 5:37 ` Eric Dumazet
2009-11-09 15:38 ` Octavian Purdila
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=20091108.205522.185944441.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=lgrijincu@ixiacom.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.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).