From: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
To: Torsten Schmidt <torsten.schmidt@s2006.tu-chemnitz.de>
Cc: netdev@vger.kernel.org
Subject: Re: Still using IPTOS_TOS() in kernel? Really???
Date: Mon, 21 Dec 2009 13:28:34 -0800 [thread overview]
Message-ID: <4B2FE882.3080207@redfish-solutions.com> (raw)
In-Reply-To: <200912212150.34727.schmto@hrz.tu-chemnitz.de>
On 12/21/2009 12:50 PM, Torsten Schmidt wrote:
> Hi Philip,
>
> here a second PATCH to add the missing DSCP classes to
> ipv4_dscp_stat(), also tested against 2.6.32.
>
> Next step is to add IN / OUT statistic to DSCP. Maybe
> /proc/net/ipdscp will look like:
> CS0 in out
> CS1 in out
> ...
> EF in out
>
>
> any comments ?
> Torsten
Hi Torsten,
Yes, the MIB changes are certainly important... we are more focused though on actually updating the default queuing strategies.
I'll poke around and see if I can figure out how that works...
Looking at include/linux/pkt_sched.h:
#define TC_PRIO_BESTEFFORT 0
#define TC_PRIO_FILLER 1
#define TC_PRIO_BULK 2
#define TC_PRIO_INTERACTIVE_BULK 4
#define TC_PRIO_INTERACTIVE 6
#define TC_PRIO_CONTROL 7
it seems that these TC priorities are just random, unrelated buckets and their ordinality has no relation to their priority. Is that correct?
If that's the case, then you *can't* just do:
static inline char rt_dscp2priority(u8 tos)
{
return IPTOS_PREC(tos)>>5;
}
for instance. No, that would be too easy. :-)
-Philip
next prev parent reply other threads:[~2009-12-21 21:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 0:53 Still using IPTOS_TOS() in kernel? Really??? Philip A. Prindeville
2009-12-17 16:24 ` Torsten Schmidt
2009-12-17 19:45 ` Philip A. Prindeville
2009-12-18 15:20 ` Torsten Schmidt
2009-12-21 20:50 ` Torsten Schmidt
2009-12-21 21:28 ` Philip A. Prindeville [this message]
2009-12-22 12:28 ` Torsten Schmidt
2009-12-23 23:09 ` Philip A. Prindeville
2010-01-05 15:35 ` Torsten Schmidt
2010-01-05 18:20 ` Philip A. Prindeville
2010-01-11 14:16 ` Torsten Schmidt
2009-12-21 21:14 ` Philip A. Prindeville
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=4B2FE882.3080207@redfish-solutions.com \
--to=philipp_subx@redfish-solutions.com \
--cc=netdev@vger.kernel.org \
--cc=torsten.schmidt@s2006.tu-chemnitz.de \
/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).