From: Mat Martineau <mathew.j.martineau at linux.intel.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [MPTCP][PATCH v7 mptcp-next 1/7] mptcp: create the listening socket for new port
Date: Thu, 03 Dec 2020 17:47:10 -0800 [thread overview]
Message-ID: <6816d41f-9856-10f1-8b61-8ca75ac1dbc@linux.intel.com> (raw)
In-Reply-To: 9bfd982aa08d39d84846b7fa655230dc11e91f1c.1606716547.git.geliangtang@gmail.com
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
On Mon, 30 Nov 2020, Geliang Tang wrote:
> This patch created a listening socket when an address with a port-number
> is added by PM netlink. Then binded the new port to the socket, and
> listened for the connection.
>
> Signed-off-by: Geliang Tang <geliangtang(a)gmail.com>
> ---
> net/mptcp/pm_netlink.c | 58 ++++++++++++++++++++++++++++++++++++++++++
> net/mptcp/protocol.c | 2 +-
> net/mptcp/protocol.h | 3 +++
> net/mptcp/subflow.c | 4 +--
> 4 files changed, 64 insertions(+), 3 deletions(-)
>
Another thing I don't think we discussed yet with this "extra listening
socket" approach: what do we do about socket options?
Are there any options we should be concerned about on this listening
socket? Should SO_REUSEADDR be set by default?
--
Mat Martineau
Intel
next reply other threads:[~2020-12-04 1:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-04 1:47 Mat Martineau [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-14 4:22 [MPTCP] Re: [MPTCP][PATCH v7 mptcp-next 1/7] mptcp: create the listening socket for new port Geliang Tang
2020-12-11 15:21 Paolo Abeni
2020-12-10 3:48 Geliang Tang
2020-12-09 15:25 Paolo Abeni
2020-12-09 12:33 Geliang Tang
2020-12-09 11:24 Geliang Tang
2020-12-09 11:13 Paolo Abeni
2020-12-09 10:27 Geliang Tang
2020-12-08 15:39 Paolo Abeni
2020-12-07 6:30 Geliang Tang
2020-12-04 10:21 Paolo Abeni
2020-12-04 1:36 Mat Martineau
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=6816d41f-9856-10f1-8b61-8ca75ac1dbc@linux.intel.com \
--to=unknown@example.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 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.