From: Stephen Hemminger <shemminger@vyatta.com>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>
Cc: David Miller <davem@davemloft.net>, 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 08:22:54 -0800 [thread overview]
Message-ID: <20130103082254.770d4222@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <20130103125812.GJ4464@order.stressinduktion.org>
On Thu, 3 Jan 2013 13:58:12 +0100
Hannes Frederic Sowa <hannes@stressinduktion.org> wrote:
> On Thu, Jan 03, 2013 at 04:53:50AM -0800, David Miller wrote:
> > From: Hannes Frederic Sowa <hannes@stressinduktion.org>
> > Date: Thu, 3 Jan 2013 13:28:44 +0100
> >
> > > On Thu, Jan 03, 2013 at 01:00:09AM +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.
> > >
> > > May I ask what lead to the rejection of the patch?
> >
> > I don't see any value in splitting up ipv4 and ipv6.
> >
> > I think we should turn the existing knob on unliaterally
> > by default. That would be a much better patch.
>
> Oh, I would be happy to do that. :)
Perhaps, ECN should be a property of the route.
There is RTAX_FEATURE_ECN but it appears to have been lost
as part of the removal of route cache.
next prev parent reply other threads:[~2013-01-03 16:24 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 [this message]
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
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=20130103082254.770d4222@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--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.