From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tail and head drop qdiscs
Date: Thu, 27 Jan 2005 13:21:25 +0000 [thread overview]
Message-ID: <41F8EAD5.1080706@dsl.pipex.com> (raw)
In-Reply-To: <1106170939.10019.23.camel@localhost.localdomain>
vincent perrier wrote:
>>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 ...
>
>
>>What sort of thing do you want this for?
>>...
>>Andy.
>>
>
>
> Very low rate (satellite links for example) and strict priority can
> lead to messages waiting for a chance to be transmitted and getting
> old in low prio queues as higher priority messages take all the
> bandwidth.
> Vincent.
Ahh - if the messages established tcp then I don't think it will make
any difference.
If the messages are udp then I suppose it could help a bit - depends
what you mean by messages.
Andy.
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-27 13:21 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
2005-01-25 19:41 ` vincent perrier
2005-01-27 13:21 ` Andy Furniss [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=41F8EAD5.1080706@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox