From: Simon Tennant <simon@imaginator.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Choosing a qlen?
Date: Tue, 22 Jan 2008 09:50:22 +0000 [thread overview]
Message-ID: <4795BC5E.8080304@imaginator.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 762 bytes --]
qlen must be the worst term to search for on the internet: the results
show endless ifconfig output.
I am trying to work out the optimal qlen for:
* ADSL outbound
* wireless outbound.
My current understanding is that it is the buffer in the kernel before
the packets hit the buffer on the ethernet card. So a nice fat qlen
should allow better traffic prioritisation? Or am I misguided?
If it helps, I'm trying to prioritise traffic and reduce jitter between
my asterisk box on the internet and my wifi voip fone hanging off an
internal subnet.
S.
--
Simon Tennant _____________________________________________
fixed: .uk +44 20 7043 6756 .de +49 89 420 955 854
mob: .uk +44 79 6096 6249 .de +49 17 8545 0880
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 249 bytes --]
[-- Attachment #2: Type: text/plain, Size: 143 bytes --]
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2008-01-22 9:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4795BC5E.8080304@imaginator.com \
--to=simon@imaginator.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