From: Eric Dumazet <eric.dumazet@gmail.com>
To: Changli Gao <xiaosuo@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Tom Herbert <therbert@google.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH] RPS: support 802.1q and pppoe session
Date: Thu, 25 Mar 2010 06:58:25 +0100 [thread overview]
Message-ID: <1269496705.15280.89.camel@edumazet-laptop> (raw)
In-Reply-To: <412e6f7f1003242247h79dd3ce0u449a1e71bf4ec742@mail.gmail.com>
Le jeudi 25 mars 2010 à 13:47 +0800, Changli Gao a écrit :
> Yea, we do DPI in netfilter. And for a stateful fireware, connection
> tracking isn't cheap. As bandwidth increases, we find one CPU can't
> handle all the traffic from a single NIC. We currently use dynamic
> weighted packets distributing algorithm with patched Linux-2.6.18, and
> it works very well.
>
Hmm... we added RCU to conntrack last year only, so with 2.6.18
conntrack hits a global lock.
tcp conntrack also uses another global lock, this is not yet converted,
even in 2.6.33.
How can this scale ?
> Oh, maybe I misunderstood you words. I thought the rxhash you want to
> clear is computed by get_rps_cpu()? I remembered some NIC itself can
> get 5-tuple from vlan and pppoe packets to compute hash. In that case,
> we should not clear rxhash.
>
rxhash is provided/computed only if its possible, and stay 0 if its not
possible to compute it :)
AFAIK, at this point, no network driver currently provides a rxhash. If
you know some NIC can provide it, please submit a patch :)
next prev parent reply other threads:[~2010-03-25 5:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 4:30 [PATCH] RPS: support 802.1q and pppoe session Changli Gao
2010-03-25 4:50 ` David Miller
2010-03-25 5:03 ` Eric Dumazet
2010-03-25 5:12 ` Changli Gao
2010-03-25 5:24 ` Eric Dumazet
2010-03-25 5:47 ` Changli Gao
2010-03-25 5:58 ` Eric Dumazet [this message]
2010-03-25 6:09 ` Changli Gao
2010-03-25 5:13 ` Eric Dumazet
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=1269496705.15280.89.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.com \
--cc=xiaosuo@gmail.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