From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: [RFC] Implementing an additional TCP congestion control algorithm (TCP-PR) - communication and organisation.
Date: Thu, 13 Aug 2015 17:48:01 +0200 [thread overview]
Message-ID: <20150813154801.GA4336@grml> (raw)
In-Reply-To: <55CAA217.4080606@Student.Uni-Augsburg.DE>
Hi!
On 03:32 Wed 12 Aug , Richard Sailer wrote:
> Hello,
> I'm Richard Sailer and I've started implementing an alternative congestion control algorithm for linux,
> capable of maintaining high throughput during persistent packet reordering (TCP-PR).
I am not a maintainer and I am not that familiar with TCP, but if you want my
opinion: Dealing with reordering inside congestion control sounds rather
weird. If reordering causes TCP to believe packets are lost, there will
probably be other issues as well, like sending of useless retransmits. I would
rather try to detect this kind of reordering and ignore dupacks and rely only
on timeouts to detect loss. Also, the recipient may send an ack for each
incoming data packet instead of delaying+combine acks.
-Michi
--
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com
next prev parent reply other threads:[~2015-08-13 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 1:32 [RFC] Implementing an additional TCP congestion control algorithm (TCP-PR) - communication and organisation Richard Sailer
2015-08-12 2:06 ` Greg KH
2015-08-13 15:48 ` michi1 at michaelblizek.twilightparadox.com [this message]
2015-08-16 14:41 ` [RFC] Implementing an additional TCP congestion control algorithm (TCP-PR) Richard Sailer
2015-08-17 19:32 ` michi1 at michaelblizek.twilightparadox.com
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=20150813154801.GA4336@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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 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.