All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH v2] tcp: split tcp_ecn sysctl knob to distinguish between IPv4 and IPv6
Date: Thu, 3 Jan 2013 13:57:36 +0100	[thread overview]
Message-ID: <20130103125736.GI4464@order.stressinduktion.org> (raw)
In-Reply-To: <1357217260.21409.24224.camel@edumazet-glaptop>

On Thu, Jan 03, 2013 at 04:47:40AM -0800, Eric Dumazet wrote:
> On Thu, 2013-01-03 at 01:00 +0100, Hannes Frederic Sowa wrote:
> > ECN could be more reliable when used with IPv6 (I don't have proofs). For
> > people who want to try ECN with IPv6 but still have problems connecting
> > to destinations because of broken IPv4 routers this switch allows one
> > to enable ECN just for IPv6.
> > 
> > Perhaps ECN could be enabled by default in future.
> > 
> > No code changes since initial submission, just added documentation.
> > 
> > Signed-off-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
> > ---
> 
> It would be nice to make the ecn sysctl per net namespace.
> 
> Do you have an idea of how to adapt your patch to get this as well ?

Currently not, but I will try. :)

Is the direction to split the sysctl ok? Or should it be a unified sysctl for
ipv4/ipv6 and only be separate per namespace?

Thanks!

  reply	other threads:[~2013-01-03 12:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-03  0:00 [PATCH v2] tcp: split tcp_ecn sysctl knob to distinguish between IPv4 and IPv6 Hannes Frederic Sowa
2013-01-03 12:28 ` Hannes Frederic Sowa
2013-01-03 12:53   ` David Miller
2013-01-03 12:58     ` Hannes Frederic Sowa
2013-01-03 16:22       ` Stephen Hemminger
2013-01-03 16:58         ` Hannes Frederic Sowa
2013-01-06  1:31     ` Hannes Frederic Sowa
2013-01-03 12:47 ` Eric Dumazet
2013-01-03 12:57   ` Hannes Frederic Sowa [this message]
2013-01-03 13:13     ` Eric Dumazet

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=20130103125736.GI4464@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.