netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Miguel Freitas <miguel@cetuc.puc-rio.br>
Cc: netdev@oss.sgi.com
Subject: Re: [Fwd: [patch] fix slot clash in sch_sfq.c]
Date: Wed, 11 Feb 2004 19:35:31 -0800	[thread overview]
Message-ID: <20040211193531.685c73c6.davem@redhat.com> (raw)
In-Reply-To: <1076532461.19204.50.camel@pitanga.ldhs.cetuc.puc-rio.br>

On Wed, 11 Feb 2004 18:47:41 -0200
Miguel Freitas <miguel@cetuc.puc-rio.br> wrote:

> I better send a copy of this one to the mailing list...

Your patch is correct.  It is amusing that sfq_drop() was handling
this correctly yet sfq_dequeue() was not.  In fact, this breaks
pretty seriously the behavior of this scheduler as you've noted.

      reply	other threads:[~2004-02-12  3:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-11 20:47 [Fwd: [patch] fix slot clash in sch_sfq.c] Miguel Freitas
2004-02-12  3:35 ` David S. Miller [this message]

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=20040211193531.685c73c6.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=miguel@cetuc.puc-rio.br \
    --cc=netdev@oss.sgi.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).