From: David Miller <davem@davemloft.net>
To: xiaosuo@gmail.com
Cc: therbert@google.com, netdev@vger.kernel.org
Subject: Re: [PATCH] RPS: support 802.1q and pppoe session
Date: Wed, 24 Mar 2010 21:50:01 -0700 (PDT) [thread overview]
Message-ID: <20100324.215001.82823131.davem@davemloft.net> (raw)
In-Reply-To: <4BAAE6E9.6030103@gmail.com>
From: Changli Gao <xiaosuo@gmail.com>
Date: Thu, 25 Mar 2010 12:30:33 +0800
> support 802.1q and pppoe session
>
> Support 802.1q and pppoe session, and these two protocols can get the
> benefit from RPS.
>
> Signed-off-by: Changli Gao <xiaosuo@gmail.com>
This is getting rediculious.
The TX hasher doesn't support this, neither should RPS.
Most of the patches you've been posting to RPS are very specialized
hacks and frankly not very welcome.
next prev parent reply other threads:[~2010-03-25 4:49 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 [this message]
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
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=20100324.215001.82823131.davem@davemloft.net \
--to=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;
as well as URLs for NNTP newsgroup(s).