From: Hagen Paul Pfeifer <hagen@jauu.net>
To: Octavian Purdila <octavian.purdila@intel.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Christoph Paasch <christoph.paasch@uclouvain.be>
Subject: Re: [RFC] Support for Multipath TCP in the Linux kernel
Date: Wed, 21 May 2014 15:32:39 +0200 [thread overview]
Message-ID: <CAPh34mdxaQ94RxAMEDpDx5Zp3gpjipO+tr_4yC-rOTq2k2TZZw@mail.gmail.com> (raw)
In-Reply-To: <CAE1zot+kBdDbYrZ9m2oCg12yUBAZvToPeDeB4aZmD65xg4e0Cg@mail.gmail.com>
IMHO, continue with 1) but try hard to reduce crossovers. MPTCP
specific functionality should be separated as possible and crossovers
(e.g. function calls) within standard TCP should be reduced to a bare
minimum. Fast paths should probably further optimized with static keys
(probability that a MPTCP socket is used is low - optimize for the
common case).
My two cents
[1] https://www.kernel.org/doc/Documentation/static-keys.txt
prev parent reply other threads:[~2014-05-21 13:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 14:23 [RFC] Support for Multipath TCP in the Linux kernel Octavian Purdila
2014-05-21 13:32 ` Hagen Paul Pfeifer [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=CAPh34mdxaQ94RxAMEDpDx5Zp3gpjipO+tr_4yC-rOTq2k2TZZw@mail.gmail.com \
--to=hagen@jauu.net \
--cc=christoph.paasch@uclouvain.be \
--cc=netdev@vger.kernel.org \
--cc=octavian.purdila@intel.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).