All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni at redhat.com>
To: mptcp at lists.01.org
Subject: [MPTCP] Re: [PATCH v2 0/2] Interim Path Manager
Date: Mon, 14 Oct 2019 13:29:11 +0200	[thread overview]
Message-ID: <fa075b41d8c5ddc20037031633dc3396989c4cbe.camel@redhat.com> (raw)
In-Reply-To: 20190917183750.2693-1-peter.krystad@linux.intel.com

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

Hi,

On Tue, 2019-09-17 at 11:37 -0700, Peter Krystad wrote:
> Patchset includes the interim path manager plus sysctl setting of
> the announce address and binding local address when creating subflows.
> I also split the path manager into a seperate file.
> 
> v2:
>   rename to 'basic' path manager
>   remove pm_init definition
>     
> Peter Krystad (2):
>   mptcp: Minor changes to path manager interface
>   mptcp: Implement basic path manager
> 
>  net/mptcp/Makefile   |   2 +-
>  net/mptcp/basic.c    | 247 +++++++++++++++++++++++++++++++++++++++++++
>  net/mptcp/pm.c       |  38 +++++--
>  net/mptcp/protocol.c |   2 +-
>  net/mptcp/protocol.h |  14 ++-
>  5 files changed, 290 insertions(+), 13 deletions(-)
>  create mode 100644 net/mptcp/basic.c

I'm sorry for lagging behind so much.

I'm ok with the patches in the current status - even if I fear some
rebasing will be now need, perhaps good Matt can take that bourden, too
 - since he called me 'lawyer' I feel less guilty asking that ;)

I think we pm looking schema may need some follow-up/cleanup, but that
could eventually follow later.

Cheers,

Paolo

             reply	other threads:[~2019-10-14 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14 11:29 Paolo Abeni [this message]
2019-10-14 16:36 [MPTCP] Re: [PATCH v2 0/2] Interim Path Manager Matthieu Baerts
2019-10-15  4:40 Peter Krystad

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=fa075b41d8c5ddc20037031633dc3396989c4cbe.camel@redhat.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.