netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: torsten.schmidt@s2006.tu-chemnitz.de
Cc: netdev@vger.kernel.org, philipp_subx@redfish-solutions.com
Subject: Re: [PATCH] ipv4: add DiffServ priority based routing
Date: Tue, 12 Jan 2010 12:16:07 -0800 (PST)	[thread overview]
Message-ID: <20100112.121607.39835310.davem@davemloft.net> (raw)
In-Reply-To: <201001121432.43301.schmto@hrz.tu-chemnitz.de>


You can't do any of these things you are doing, I've basically been
ignoring all of these crazy diffserv patches, they're nuts!

The TOS socket option has a meaning and behavior defined by the BSD
sockets interface many years ago.  And you cannot and must not change
the behavior of those system calls because applications are written to
the current behavior and you will break them.  Protecting the new
behavior with a kernel config option is a non-starter, it's pointless
because no distribution is going to enable a kernel option that
knowingly breaks applications.

And it is also possible to set the TOS field however you desire using
what the kernel currently provides, we do not preclude proper diffserv
support, the BSD socket interfaces allow that just fine.

And you can also do diffserv by classifying traffic and setting the
TOS field using either the packet scheduler, or even netfilter.

Linux supports diffserv fully and just fine, you just can't see it :-)

Please stop submitting these patches without first having at least a
real discussion and understanding of how this stuff works.

Thanks.

  reply	other threads:[~2010-01-12 20:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-12 13:32 [PATCH] ipv4: add DiffServ priority based routing Torsten Schmidt
2010-01-12 20:16 ` David Miller [this message]
2010-01-12 20:59   ` Philip A. Prindeville
2010-01-12 21:03     ` David Miller
2010-01-12 21:33       ` Philip A. Prindeville
2010-01-13  4:47         ` Steven Blake
2010-03-11 19:25       ` Philip A. Prindeville
2010-03-11 19:29         ` David Miller
2010-03-11 19:32           ` Philip A. Prindeville
2010-03-12 11:18           ` Benny Amorsen
2011-02-21  6:01             ` Philip Prindeville
2010-01-14 11:50   ` Torsten Schmidt
2010-01-14 12:50     ` Eric Dumazet
2010-01-15  0:51       ` David Miller
2010-01-15  8:24         ` Eric Dumazet
2010-01-15  8:26           ` David Miller

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=20100112.121607.39835310.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=netdev@vger.kernel.org \
    --cc=philipp_subx@redfish-solutions.com \
    --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).