netdev - Re: [RFC] Support for Multipath TCP in the Linux kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPh34mdxaQ94RxAMEDpDx5Zp3gpjipO+tr_4yC-rOTq2k2TZZw@mail.gmail.com>
Date:	Wed, 21 May 2014 15:32:39 +0200
From:	Hagen Paul Pfeifer <hagen@...u.net>
To:	Octavian Purdila <octavian.purdila@...el.com>
Cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	Christoph Paasch <christoph.paasch@...ouvain.be>
Subject: Re: [RFC] Support for Multipath TCP in the Linux kernel

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html