From: Max Krasnyanskiy <maxk@qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: therbert@google.com, netdev@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: RFC [PATCH net-2.6 1/6] net: Scheduling softirqs between CPUSs
Date: Fri, 07 Mar 2008 11:02:31 -0800 [thread overview]
Message-ID: <47D19147.9070609@qualcomm.com> (raw)
In-Reply-To: <20080305.132112.01598419.davem@davemloft.net>
David Miller wrote:
> From: therbert@google.com (Tom Herbert)
> Date: Wed, 5 Mar 2008 12:51:16 -0800 (PST)
>
>> This patch implements kernel changes to allow scheduling of softirq's between processors.
>>
>> Signed-off-by: Tom Herbert <therbert@google.com>
>
> I've stated this in the past and I still feel that it is foolish to
> put all of this code into the kernel when every single piece of
> networking hardware will be doing this for us transparently.
>
> Maybe if someone had proposed this 4 or 5 years ago, but right now
> this code will be irrelevant by the time it ships to any real users.
Plus it seems that for this kind of stuff it be better to replace network
softirq with kthreads (like in -rt kernel) and let the scheduler take care of
the load balancing. More flexible and scalable.
I'd suggest for your to play with -rt kernel and see if it already does what
you need.
Max
next prev parent reply other threads:[~2008-03-07 19:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-05 20:51 RFC [PATCH net-2.6 1/6] net: Scheduling softirqs between CPUSs Tom Herbert
2008-03-05 21:21 ` David Miller
2008-03-07 19:02 ` Max Krasnyanskiy [this message]
2008-03-10 23:26 ` Tom Herbert
2008-03-11 1:06 ` Brandeburg, Jesse
2008-03-11 16:20 ` Tom Herbert
2008-03-11 16:52 ` Ben Hutchings
2008-03-11 23:48 ` Tom Herbert
2008-03-12 15:10 ` Ben Hutchings
2008-03-13 3:41 ` David Miller
2008-03-13 11:47 ` Ben Hutchings
2008-03-13 12:53 ` 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=47D19147.9070609@qualcomm.com \
--to=maxk@qualcomm.com \
--cc=davem@davemloft.net \
--cc=mingo@elte.hu \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.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).