From: David Miller <davem@davemloft.net>
To: elelueck@linux.vnet.ibm.com
Cc: eric.dumazet@gmail.com, netdev@vger.kernel.org,
ubacher@de.ibm.com, raspl@de.ibm.com, frankbla@de.ibm.com,
samudrala@us.ibm.com
Subject: Re: [RFC PATCH V2] tcp: introduce raw access to experimental options
Date: Tue, 08 Jan 2013 14:30:12 -0800 (PST) [thread overview]
Message-ID: <20130108.143012.1830129306456354509.davem@davemloft.net> (raw)
In-Reply-To: <50EC2EF3.5080506@linux.vnet.ibm.com>
I just want you to know that I've very displeased with this
feature.
These things belong in a controlled environment in our TCP stack, so
hack our TCP stack if you want to play with experimental TCP options.
I do not want to add ways to poke around, either via socket options
or completely opaque interfaces exported to modules, with TCP options.
Sorry.
prev parent reply other threads:[~2013-01-08 22:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 16:13 [RFC PATCH V2] tcp: introduce raw access to experimental options elelueck
2013-01-07 16:13 ` elelueck
2013-01-07 16:44 ` Eric Dumazet
2013-01-08 14:36 ` Einar Lueck
2013-01-08 22:30 ` David Miller [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=20130108.143012.1830129306456354509.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=elelueck@linux.vnet.ibm.com \
--cc=eric.dumazet@gmail.com \
--cc=frankbla@de.ibm.com \
--cc=netdev@vger.kernel.org \
--cc=raspl@de.ibm.com \
--cc=samudrala@us.ibm.com \
--cc=ubacher@de.ibm.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).