From: Brian Brandon <Brian@vUnity.com>
To: 'David Miller' <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: RE: MPTCP Kernel Developer
Date: Fri, 10 Apr 2015 01:29:52 +0000 [thread overview]
Message-ID: <bde533c5bbef43b6815e8cbdf51b6365@mail.vUnity.com> (raw)
In-Reply-To: <20150409.202637.1489346008975456388.davem@davemloft.net>
David,
We have been successful building a new unreliable MPTCP and the RTT packet scheduler functions correctly with retransmits while discarding the acknowledgement (thereby avoiding the dreaded TCP Congestion Collapse.) However, we can't get it stable in the Linux kernel yet.
We believe a scalable MPTCP proxy is of major significance and we're contributing everything we build back to the community. -- it's not some corporate headhunt stuff. We're honestly just stuck for now and didn't know where else to turn but back to the community for some help.
-Brian
Brian J. Brandon
CCNP | MCSE:Security | MCITP:EA
Bandwidth | Reliability | Efficiency | Unified
-----Original Message-----
From: David Miller [mailto:davem@davemloft.net]
Sent: Thursday, April 09, 2015 5:27 PM
To: Brian Brandon
Cc: netdev@vger.kernel.org
Subject: Re: MPTCP Kernel Developer
From: Brian Brandon <Brian@vUnity.com>
Date: Thu, 9 Apr 2015 22:58:35 +0000
> Anybody know a veteran Linux kernel developer available for some part
> time work?
This is absolutely not appropriate for this mailing list.
Please do not do this again.
next prev parent reply other threads:[~2015-04-10 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 22:58 MPTCP Kernel Developer Brian Brandon
2015-04-10 0:26 ` David Miller
2015-04-10 1:29 ` Brian Brandon [this message]
2015-04-10 2:00 ` Eric Dumazet
2015-04-10 2:29 ` David Miller
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=bde533c5bbef43b6815e8cbdf51b6365@mail.vUnity.com \
--to=brian@vunity.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).