public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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: Thu, 17 Dec 2009 11:45:32 -0800	[thread overview]
Message-ID: <4B2A8A5C.9070702@redfish-solutions.com> (raw)
In-Reply-To: <200912171724.32711.schmto@hrz.tu-chemnitz.de>

On 12/17/2009 08:24 AM, Torsten Schmidt wrote:
> Hi Philip,
> 
> interesting .. i am on the way to implement a DSCP/CS statistic to the kernel. 
> We need this for network traffic accounting. The concept is the following: 
> 
> We create a virtual file /pro/net/ipdscp , this includes several DSCP/CS 
> counters. See http://www.iana.org/assignments/dscp-registry/. Every time 
> ip_rcv_finish() is called, we take a look at the DSCP/CS (iph->tos) value and 
> increment the related counter. If you're interested in, i will send you a 
> patch ? ..  

That would be great.

> Maybe this is a good starting point for an DSCP/CS implementation. I was also 
> shocked that the kernel do not really handle DiffServ thinks. 

I think it would also be useful to rework the existing definition of rt_tos2priority() to have a DSCP/CS version that people could then select and build in their kernel via a simple CONFIG_DIFFSERV_COMPLIANT flag.

It could be selectable and default to off until a set cut-over point in the future, then it could become the default.

RFC-2474 is now 11 years old...  Odd that we're still not compliant.

-Philip


>> Assuming my crusade to get various common apps and services (wget, TB, FF,
>>  Sendmail, Cyrus, ProFTPd, etc) to use DSCP/CS marking (very few apps
>>  currently use DSCP or precedence marking), then kernels with the proper
>>  default behavior will need to start shipping, right?  I.e. out-of-the-box
>>  kernels should handle such apps without further configuration, such as
>>  needing to have the DSCP iptables module installed.  They should "just
>>  work".
> Right. 
> 
> Best regards,
> Torsten


  reply	other threads:[~2009-12-17 19:45 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 [this message]
2009-12-18 15:20     ` Torsten Schmidt
2009-12-21 20:50     ` Torsten Schmidt
2009-12-21 21:28       ` Philip A. Prindeville
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=4B2A8A5C.9070702@redfish-solutions.com \
    --to=philipp_subx@redfish-solutions$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=torsten.schmidt@s2006$(echo .)tu-chemnitz.de \
    /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