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] [PATCH 0/3] mptcp: refactor xmit path
Date: Mon, 15 Apr 2019 17:30:46 +0200	[thread overview]
Message-ID: <cover.1555342070.git.pabeni@redhat.com> (raw)

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

his series refactor the mptcp xmit path trying to make sendmsg behavior
more consistent, memory efficent and improve its performances.

The code is also available here:

https://github.com/pabeni/mptcp/tree/mptcp-proposal-devel

To support MP_JOIN and multiple subflows, the idea is adding, with later
patches, an RB-tree structure containing references to the pending page
fragments, their length and the associated mptcp write_seq number (is subflow
rel_write_seq needed, too?). RB-tree node can be allocated using the same
page frag used in this series for skb data. Each RB-tree node will own a
reference to the page frag.

RFC -> v1:
 - addressed Mat's feedback, dropping patch 3/4 and switching
   to per msk page frag use, and checking mptcp seq number for coalescing

Paolo Abeni (3):
  mptcp: use sk_page_frag() in sendmsg
  mptcp: sendmsg() do spool all the provided data
  mptcp: allow collapsing consecutive sendpages on the same substream

 net/mptcp/protocol.c | 181 ++++++++++++++++++++++++++++---------------
 1 file changed, 119 insertions(+), 62 deletions(-)

-- 
2.20.1


             reply	other threads:[~2019-04-15 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-15 15:30 Paolo Abeni [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-04-18 23:58 [MPTCP] [PATCH 0/3] mptcp: refactor xmit path Mat Martineau
2019-05-07 13:15 Paolo Abeni
2019-05-07 16:06 Paolo Abeni

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=cover.1555342070.git.pabeni@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.