From: Changli Gao <xiaosuo@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Tom Herbert <therbert@google.com>,
davem@davemloft.com, netdev@vger.kernel.org
Subject: Re: [PATCH v2] rfs: Receive Flow Steering
Date: Tue, 6 Apr 2010 21:42:54 +0800 [thread overview]
Message-ID: <u2n412e6f7f1004060642h56e60069k9fb896d273df56d1@mail.gmail.com> (raw)
In-Reply-To: <1270559096.2081.35.camel@edumazet-laptop>
On Tue, Apr 6, 2010 at 9:04 PM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>
> 1) The need to add "rps_flow_entries=xxx" at boot time is problematic.
> Maybe we can allow it being dynamic (and use vmalloc() instead of
> alloc_large_system_hash())
Is flex_array better than vmalloc()?
--
Regards，
Changli Gao(xiaosuo@gmail.com)
next prev parent reply other threads:[~2010-04-06 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-06 5:56 [PATCH v2] rfs: Receive Flow Steering Tom Herbert
2010-04-06 13:04 ` Eric Dumazet
2010-04-06 13:42 ` Changli Gao [this message]
2010-04-06 14:25 ` Tom Herbert
2010-04-06 15:10 ` Eric Dumazet
2010-04-08 4:40 ` David 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=u2n412e6f7f1004060642h56e60069k9fb896d273df56d1@mail.gmail.com \
--to=xiaosuo@gmail.com \
--cc=davem@davemloft.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=therbert@google.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).