All of lore.kernel.org
 help / color / mirror / Atom feed
From: jamal <hadi@cyberus.ca>
To: David Miller <davem@davemloft.net>
Cc: krkumar2@in.ibm.com, netdev@vger.kernel.org
Subject: Re: [PATCH] sched: Optimize return value of qdisc_restart
Date: Wed, 09 May 2007 08:56:43 -0400	[thread overview]
Message-ID: <1178715404.4073.21.camel@localhost> (raw)
In-Reply-To: <20070509.011201.68040843.davem@davemloft.net>

On Wed, 2007-09-05 at 01:12 -0700, David Miller wrote:

> Something this evening is obviously making it impossible
> for my brain to understand this function and your patch,
> so I'm going to sleep on it and try again tomorrow :-)

It is one of those areas that are hard to size-up in a blink;->
Gut-feeling: It doesnt sit right with me as well.
 
With (2.6.18-rxX++) QDISC_RUNNING changes that mean only one of N CPUs
will be dequeueing while the N-1 maybe enqueueing concurently. All N
CPUs contend for the queue lock; and theres a possible window between
releasing the queue lock by the dequeuer-CPU and enqueuer-CPU for a
race. The dequeuer-CPU entering one last time helps.

Krishna, you probably saw this "wasted entry into qdisc" under low
traffic conditions with more than likely only one CPU sending, am i
correct? Under heavier traffic when we have multiple CPUs funneling to
the same device, that entry is not really a "waste" because we endup
only go in once per X number of packets enqueued on the qdisc and that
check is absolutely necessary because a different CPU may have enqueued
while you were not looking. In the case of low traffic, X=1 - so it is a
waste there albeit a necessary one.

cheers,
jamal



  reply	other threads:[~2007-05-09 12:56 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-08  7:31 [PATCH] sched: Optimize return value of qdisc_restart Krishna Kumar
2007-05-09  2:05 ` David Miller
2007-05-09  4:35   ` Krishna Kumar2
2007-05-09  6:36     ` David Miller
2007-05-09  7:23       ` Krishna Kumar2
2007-05-09  8:12         ` David Miller
2007-05-09 12:56           ` jamal [this message]
2007-05-09 14:47             ` Krishna Kumar2
2007-05-09 15:52               ` jamal
2007-05-10  5:12                 ` Krishna Kumar2
2007-05-10 11:50                   ` Herbert Xu
2007-05-10 11:55                     ` David Miller
2007-05-10 12:10                       ` Herbert Xu
2007-05-10 21:11                         ` David Miller
2007-05-10 12:21                       ` jamal
2007-05-10 12:50                         ` jamal
2007-05-10 12:59                         ` Herbert Xu
2007-05-10 13:18                           ` jamal
2007-05-10 13:52                             ` Herbert Xu
2007-05-10 14:12                               ` jamal
2007-05-10 14:26                                 ` Krishna Kumar2
2007-05-10 14:31                                   ` Herbert Xu

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=1178715404.4073.21.camel@localhost \
    --to=hadi@cyberus.ca \
    --cc=davem@davemloft.net \
    --cc=krkumar2@in.ibm.com \
    --cc=netdev@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.