User Details
- User Since
- Jan 22 2015, 5:22 AM (264 w, 6 d)
Yesterday
Update comments and name of the mss function per the comments in the review.
Wed, Feb 12
Address Hans comments, also fix the issue I had
when I back things out (the net epoch macro should have
been in the source).. also add just a few more comments and
fix a spelling error in one.
Fri, Jan 24
Jan 8 2020
Jan 6 2020
Commited
Dec 18 2019
Dec 17 2019
I am happy with one commit that cleans it all up :)
Dec 4 2019
Nov 22 2019
Nov 21 2019
You cannot use tcp_compute_pipe() with rack. It does not use
the same variables as the default stack. Instead you must use the
ctf_flight_size() function to get whats in flight.
Nov 2 2019
Oct 24 2019
Oct 14 2019
Oct 6 2019
Sep 28 2019
Well I am going to voice a different view. I do *not* see this as a nice cleanup. I see it
has a lessening of information.
Sep 24 2019
Sep 23 2019
Sep 20 2019
Sep 17 2019
This updates the patch set, the ktls.h information was incorrect. I also add the fixes
that Michael is doing on the Rack side to BBR as well (check for invalid length in non-tso case).
Sep 11 2019
Sep 10 2019
Sep 9 2019
I would like to see the Rack version of the code be identical to the tcp_input version.. i.e. it should check
Sep 6 2019
Sep 3 2019
First version was missing a (void) in the registration function.. opps
This adds a simple registration mechanism that stacks can use as they successfully register/deregister to
make the LRO code aware if any stack wants to use mbuf-queueing per Drew's suggestion.
Aug 26 2019
Aug 21 2019
Aug 15 2019
One more update, mainly comments but we also fix a couple of things
- The timestamp provided via the ctf common functions should be the real time not something from the mbuf, we let the transports look at those flags (which both BBR and the latest Rack do).
- We also for LRO add a gating of the number of acks (currently set to infinity) that can also cause a wakeup.
Aug 13 2019
The LRO patch was missing data and length limits for input processing via
MBUF_QUEUE methods. This update adds that and an elaborate set of
comments to the rack_bbr_common.c module describing in detail what
a transport designer using MBUF_QUEUEING needs to contemplate.
Aug 2 2019
Aug 1 2019
Jul 29 2019
Please validate the rack_bbr_common.c has (or does not have) the extra bit you added in the early part.
I plan on commiting this August 1st unless I hear screams.. its been pending since July 15th....
Jul 21 2019
Update to address Michael's comments about copyright (missing new magic declarations at the top) and
also address an issue where if we have an interface that marks it to "not supporting" we properly
disable the rate limiting for that interface and do not allow the user to enable it (since it does
not support it).