From: Rick Jones <rick.jones2@hp•com>
To: Tom Herbert <therbert@google•com>
Cc: Stephen Hemminger <shemminger@vyatta•com>,
davem@davemloft•net, netdev@vger•kernel.org,
eric.dumazet@gmail•com, Ingo Molnar <mingo@elte•hu>,
Paul Turner <pjt@google•com>
Subject: Re: [PATCH v4] rfs: Receive Flow Steering
Date: Fri, 16 Apr 2010 10:33:33 -0700 [thread overview]
Message-ID: <4BC89F6D.2080604@hp.com> (raw)
In-Reply-To: <o2k65634d661004160851wc00c609p7136a22fd07503c1@mail.gmail.com>
>
> This is true. There is a fundamental question of whether scheduler
> should lead networking or vice versa. The advantages of networking
> following scheduler seem to become more apparent on heavily loaded
> systems or with threads that handle more than one flow.
I will confess to being in the networking should follow the scheduler camp :)
> I'm not sure these two models have to be mutually exclusive, we are
> looking at some ways to make a hybrid model.
It is perhaps too speculative on my part, but if the host has no control over
the remote addressing of the connections to/from it, doesn't that suggest that
allowing networking to lead the scheduler gives "external forces" more say in
intra-system resource consumption than we might want them to have?
rick jones
next prev parent reply other threads:[~2010-04-16 17:33 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 [this message]
2010-04-16 17:59 ` Paul Turner
2010-04-16 18:32 ` Rick Jones
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=4BC89F6D.2080604@hp.com \
--to=rick.jones2@hp$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=eric.dumazet@gmail$(echo .)com \
--cc=mingo@elte$(echo .)hu \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pjt@google$(echo .)com \
--cc=shemminger@vyatta$(echo .)com \
--cc=therbert@google$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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