netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Westphal <fw@strlen.de>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org, Stephen Hemminger <sthemmin@microsoft.com>
Subject: Re: [RFC 0/1] tcp: constify congestion_ops
Date: Wed, 2 Aug 2017 08:00:24 +0200	[thread overview]
Message-ID: <20170802060024.GB15325@breakpoint.cc> (raw)
In-Reply-To: <20170802024943.7517-1-sthemmin@microsoft.com>

Stephen Hemminger <stephen@networkplumber.org> wrote:
> I wonder if restricting congestion control choices is still necessary?
> It seems like being overly paranoid, and better enforced by having a more
> limited kernel config, seccomp or other mechanism.

Agree, I think it can be removed.

      parent reply	other threads:[~2017-08-02  6:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-02  2:49 [RFC 0/1] tcp: constify congestion_ops Stephen Hemminger
2017-08-02  2:49 ` [RFC 1/1] constify tcp congestion Stephen Hemminger
2017-08-02  7:56   ` Eric Dumazet
2017-08-02  8:13     ` Eric Dumazet
2017-08-08 15:18       ` Stephen Hemminger
2017-08-02  6:00 ` Florian Westphal [this message]

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=20170802060024.GB15325@breakpoint.cc \
    --to=fw@strlen.de \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.com \
    /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).