All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Westphal <fw at strlen.de>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v3 7/9] mptcp: add netlink based PM
Date: Wed, 26 Feb 2020 10:36:47 +0100	[thread overview]
Message-ID: <20200226093647.GN19559@breakpoint.cc> (raw)
In-Reply-To: 415469e83738415aa2d6e99a9237c8e5468ea23c.camel@redhat.com

[-- Attachment #1: Type: text/plain, Size: 604 bytes --]

Paolo Abeni <pabeni(a)redhat.com> wrote:
> I see! Yes, currently we can't limit the number of subflows created for
> a single mptcp socket on a server. I'm unsure how bad that is, as
> usually we allow each client to create an arbitrary high number of TCP
> connection to the server (modulo syn flood).
> 
> Still I think adding the ability to impose such limit could be nice. It
> requires an additional hook (from subflow_syn_recv_sock() towards the
> PM). If we agree on that, I can try to cover in a separate
> patch/series.

I think its a must-have, as file descriptor limits don't apply.

             reply	other threads:[~2020-02-26  9:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-26  9:36 Florian Westphal [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-02-26  9:54 [MPTCP] Re: [PATCH v3 7/9] mptcp: add netlink based PM Matthieu Baerts
2020-02-26  9:51 Florian Westphal
2020-02-26  9:46 Paolo Abeni
2020-02-25 17:51 Matthieu Baerts
2020-02-24 18:31 Paolo Abeni
2020-02-24 17:58 Matthieu Baerts
2020-02-24 15:50 Paolo Abeni
2020-02-24 13:02 Matthieu Baerts
2020-02-24 12:59 Davide Caratti
2020-02-24 12:07 Paolo Abeni
2020-02-22 16:38 Matthieu Baerts

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=20200226093647.GN19559@breakpoint.cc \
    --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.