public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@vyatta•com>
To: Eric Dumazet <eric.dumazet@gmail•com>
Cc: Thomas Graf <tgraf@infradead•org>, netdev <netdev@vger•kernel.org>
Subject: Re: [RFC iproute2] sch_red: TC_RED_HARDDROP
Date: Wed, 30 Nov 2011 14:36:42 -0800	[thread overview]
Message-ID: <20111130143642.7130aa2b@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1322684749.2602.3.camel@edumazet-laptop>

On Wed, 30 Nov 2011 21:25:49 +0100
Eric Dumazet <eric.dumazet@gmail•com> wrote:

> Hi Thomas
> 
> In 2005, TC_RED_HARDDROP kernel support was added to RED and GRED
> (commit bdc450a0bb1 [PKT_SCHED]: (G)RED: Introduce hard dropping), but
> current iproute2 doesnt have user land support.
> 
> Is there some patch waiting somewhere, or should we :
> 
> - Remove kernel support, since nobody uses it.
> 
> - Add iproute2 support.

(Almost) nobody uses RED because they can't figure it out.
According to Wikipedia, VJ says that: 
 "there are not one, but two bugs in classic RED."


But if flag is present, then Thomas should have sent a patch, might have
been lost, that was pre-patchwork days.

  reply	other threads:[~2011-11-30 22:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 20:25 [RFC iproute2] sch_red: TC_RED_HARDDROP Eric Dumazet
2011-11-30 22:36 ` Stephen Hemminger [this message]
2011-12-01 21:06   ` [PATCH] sch_red: fix red_change Eric Dumazet
2011-12-01 21:35     ` Dave Taht
2011-12-01 21:48       ` Jim Gettys
2011-12-01 21:57       ` Eric Dumazet
2011-12-01 22:04         ` Jim Gettys
2011-12-05 11:42         ` Ilpo Järvinen
2011-12-07 22:57           ` Hagen Paul Pfeifer
2011-12-02  0:25     ` David Miller
2011-11-30 23:29 ` [RFC iproute2] sch_red: TC_RED_HARDDROP Thomas Graf

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=20111130143642.7130aa2b@nehalam.linuxnetplumber.net \
    --to=shemminger@vyatta$(echo .)com \
    --cc=eric.dumazet@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=tgraf@infradead$(echo .)org \
    /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