From: Stephen Hemminger <shemminger@osdl.org>
To: Hagen Paul Pfeifer <hagen@jauu.net>,
Stephen Hemminger <shemminger@osdl.org>,
David Miller <davem@davemloft.net>,
jheffner@psc.edu, netdev@vger.kernel.org
Subject: Re: [PATCH] Check if user has CAP_NET_ADMIN to change congestion control algorithm
Date: Fri, 27 Oct 2006 08:48:01 -0700 [thread overview]
Message-ID: <45422A31.7070806@osdl.org> (raw)
In-Reply-To: <20061027152157.GB4632@c3po.0xdef.net>
Hagen Paul Pfeifer wrote:
> * Stephen Hemminger | 2006-10-27 07:41:02 [-0700]:
>
>
>> Please no, it makes the socket option useless.
>>
>
> Technical no, in the sense of usability for everybody yes. You are right
> Stephen, as a programmer I understand you complete!
>
> But on the other side: We know for sure that this IS a problem if we allow
> everybody to "prefer his socket".
>
> In my opinion we should prefer fairness before usability! As John Heffner
> introduce, we can introduce a ranking system for congestion control algorithms -
> but this solution seems a little bit oversized and maybe can't be complete
> guaranteed (complex interaction between the protocols in different
> environment and so on, you know).
>
> HGN
>
>
If there is a dangerous choice, then it should be removed. Otherwise I can't
see the problem. It is a bigger risk to have to escalate the privileges
of an application
just to allow it to use something.
next prev parent reply other threads:[~2006-10-27 15:48 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 18:08 [RFC] tcp: setsockopt congestion control autoload Stephen Hemminger
2006-10-25 23:21 ` Patrick McHardy
2006-10-26 5:22 ` Evgeniy Polyakov
2006-10-26 14:34 ` Stephen Hemminger
2006-10-26 14:57 ` Evgeniy Polyakov
2006-10-26 15:23 ` Stephen Hemminger
2006-10-26 17:05 ` Patrick McHardy
2006-10-26 20:55 ` David Miller
2006-10-26 17:29 ` John Heffner
2006-10-26 20:57 ` David Miller
2006-10-26 22:44 ` Hagen Paul Pfeifer
2006-10-26 22:53 ` John Heffner
2006-10-26 23:52 ` [PATCH] Check if user has CAP_NET_ADMIN to change congestion control algorithm Hagen Paul Pfeifer
2006-10-26 23:59 ` Ian McDonald
2006-10-27 0:07 ` David Miller
2006-10-27 0:20 ` Ian McDonald
2006-10-27 0:02 ` David Miller
2006-10-27 10:43 ` Hagen Paul Pfeifer
2006-10-27 14:41 ` Stephen Hemminger
2006-10-27 15:21 ` Hagen Paul Pfeifer
2006-10-27 15:48 ` Stephen Hemminger [this message]
2006-10-27 17:30 ` [PATCH] tcp: don't allow unfair congestion control to be built without warning Stephen Hemminger
2006-10-27 17:43 ` John Heffner
2006-10-27 17:59 ` [PATCH] tcp: allow restricting congestion control choices Stephen Hemminger
2006-10-27 21:17 ` [PATCH] tcp: don't allow unfair congestion control to be built without warning David Miller
2006-10-27 21:24 ` Stephen Hemminger
2006-10-27 21:37 ` David Miller
2006-10-27 21:59 ` Stephen Hemminger
2006-10-27 22:12 ` David Miller
2006-10-27 22:21 ` Stephen Hemminger
2006-10-27 22:24 ` David Miller
2006-10-28 0:48 ` Stephen Hemminger
2006-10-28 3:10 ` [RFC] tcp: available congetsion control Stephen Hemminger
2006-10-27 21:22 ` [PATCH] Check if user has CAP_NET_ADMIN to change congestion control algorithm David Miller
2006-10-27 1:03 ` Stephen Hemminger
2006-10-27 18:14 ` [PATCH] tcp: setsockopt congestion control autoload Stephen Hemminger
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=45422A31.7070806@osdl.org \
--to=shemminger@osdl.org \
--cc=davem@davemloft.net \
--cc=hagen@jauu.net \
--cc=jheffner@psc.edu \
--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.