All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tail and head drop qdiscs
Date: Tue, 25 Jan 2005 12:32:17 +0000	[thread overview]
Message-ID: <41F63C51.9050207@dsl.pipex.com> (raw)
In-Reply-To: <1106170939.10019.23.camel@localhost.localdomain>

vincent perrier wrote:
> I think that there are no qdiscs that permit to drop the oldest
> frame of a queue when this queue is full, but I would like to
> be wrong: 
> 
> bfifo drops arriving frames when the max queue length is reached. 
> 
> red also drops arriving frames in a more elaborate fashion, with
> a drop probability that increases above a limit and becomes 
> a drop certitude when the max queue length is reached.
> 
> sfq drops "fairly", it piles frames with same (ip source, ip dest, 
> port source and port dest) and drops a frame from the
> biggest pile to favour the smaller flows. 
> 
> But I cannot find the qdisc that reacts like a bfifo or red qdisc
> but drops the oldest message of the queue when a drop is needed.
> 
> Even better: a qdisc with an autodestruct algorithm for each
> frame in the queue that would garantee the "freshness" of 
> each frame coming out. 
> 
> If you know of such qdiscs, please share.
>  

What sort of thing do you want this for?

I made a version of esfq head drop for use in specific circumstances.

The only other thing I thought head drop generally could be usefull for 
is a game server, but then maybe a policer would be better than a queue 
WRT latency.

Andy.

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  reply	other threads:[~2005-01-25 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-19 21:42 [LARTC] tail and head drop qdiscs vincent perrier
2005-01-25 12:32 ` Andy Furniss [this message]
2005-01-25 19:41 ` vincent perrier
2005-01-27 13:21 ` Andy Furniss

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=41F63C51.9050207@dsl.pipex.com \
    --to=andy.furniss@dsl.pipex.com \
    --cc=lartc@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.