From: Rick Jones <rick.jones2@hp.com>
To: Paul Turner <pjt@google.com>
Cc: Tom Herbert <therbert@google.com>,
Stephen Hemminger <shemminger@vyatta.com>,
davem@davemloft.net, netdev@vger.kernel.org,
eric.dumazet@gmail.com, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH v4] rfs: Receive Flow Steering
Date: Fri, 16 Apr 2010 11:32:36 -0700 [thread overview]
Message-ID: <4BC8AD44.9050707@hp.com> (raw)
In-Reply-To: <i2oed628a921004161059z65a3cf1aq5f3cd2194f40a811@mail.gmail.com>
> Even under a hybrid model I think phrasing it as networking leading
> the scheduler here is a little strong. The scheduler is in both cases
> the most 'informed' place to make these decisions, but I think it
> could benefit from more knowledge. In the 'virgin' single flow case
> without any steering the network stack is currently able to implicitly
> hint to the scheduler where flows could be most efficiently served due
> to wake-affine balancing behaviors. This is a natural side-effect of
> wake-ups being sourced by the networking cpus.
Hinting to the scheduler is fine - so long as the final say is the scheduler.
Presumably it is the thing that knows about the other forces tugging at where to
run the thread - where its memory is allocated, what other flows are coming to
it etc.
rick jones
next prev parent reply other threads:[~2010-04-16 18:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-13 0:03 [PATCH v4] rfs: Receive Flow Steering Tom Herbert
2010-04-13 0:12 ` Stephen Hemminger
2010-04-16 15:51 ` Tom Herbert
2010-04-16 17:33 ` Rick Jones
2010-04-16 17:59 ` Paul Turner
2010-04-16 18:32 ` Rick Jones [this message]
2010-04-13 8:45 ` 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=4BC8AD44.9050707@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=pjt@google.com \
--cc=shemminger@vyatta.com \
--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).