public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Kravetz <mkravetz@sequent.com>
To: J Sloan <jjs@toyota.com>
Cc: Rik van Riel <riel@conectiva.com.br>,
	"'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: How to optimize routing performance
Date: Thu, 15 Mar 2001 11:44:25 -0800	[thread overview]
Message-ID: <20010315114425.C1060@w-mikek2.sequent.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0103152304570.1320-100000@duckman.distro.conectiva> <3AB1153F.802BEBA9@toyota.com>
In-Reply-To: <3AB1153F.802BEBA9@toyota.com>; from jjs@toyota.com on Thu, Mar 15, 2001 at 11:17:19AM -0800

On Thu, Mar 15, 2001 at 11:17:19AM -0800, J Sloan wrote:
> Rik van Riel wrote:
> 
> > On Thu, 15 Mar 2001, J Sloan wrote:
> >
> > > There are some scheduler patches that are not part of the
> > > main kernel tree at this point (mostly since they have yet to
> > > be optimized for the common case) which make quite a big
> > > difference under heavy load - you might want to check out:
> > >
> > >     http://lse.sourceforge.net/scheduling/
> >
> > Unrelated.   Fun, but unrelated to networking...
> 
> Fun, yes, and perhaps not directly related, however
> under high load, where the sheer numbet of interrupts
> per second begins to overwhelm the kernel, might it
> not be relevant? After all, the benchmarks do point to
> tangible improvements in the performance of network
> server apps.

I'm not sure if these patches would be of any use here.

One benefit of the multi-queue scheduling patches is that
they allow multiple 'wakeups' to run in parallel instead
of being serialized by the global runqueue lock.  Now if
you are getting lots of interrupts which result in task
wakeups that could potentially be run in parallel (on
separate CPUS with no other serialization in the way)
then you 'might' see some benefit.  Those are some big IFs.

I know little about the networking stack or this workload.
Just wanted to explain how this scheduling work 'could'
be related to interrupt load.

-- 
Mike Kravetz                                 mkravetz@sequent.com
IBM Linux Technology Center

  parent reply	other threads:[~2001-03-15 19:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-15  7:23 How to optimize routing performance Mårten Wikström
2001-03-15 12:32 ` Rik van Riel
2001-03-15 16:20   ` Martin Josefsson
2001-03-15 18:09 ` J Sloan
2001-03-16  2:05   ` Rik van Riel
2001-03-15 19:17     ` J Sloan
2001-03-15 19:36       ` Gregory Maxwell
2001-03-15 19:45         ` J Sloan
2001-03-15 19:44       ` Mike Kravetz [this message]
2001-03-16  2:35       ` Rik van Riel
2001-03-15 19:28         ` J Sloan
  -- strict thread matches above, loose matches on Subject: below --
2001-03-15 14:19 Robert Olsson
2001-03-16  0:38 ` Rik van Riel
2001-03-15 18:45   ` Robert Olsson
2001-03-15 19:30   ` Jonathan Morton
2001-03-15 19:54     ` Robert Olsson
2001-03-15 21:01       ` jamal
2001-03-15 20:16 Jonathan Earle
     [not found] <3AB12640.79E7B4FB@colorfullife.com>
2001-03-15 21:39 ` Robert Olsson
2001-03-16  7:21 Mårten Wikström
2001-03-16  8:08 ` Martin Josefsson

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=20010315114425.C1060@w-mikek2.sequent.com \
    --to=mkravetz@sequent.com \
    --cc=jjs@toyota.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@conectiva.com.br \
    /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