- User Since
- May 11 2014, 7:08 PM (341 w, 3 d)
Tue, Nov 24
Mon, Nov 23
Apologies for the delayed reaction...
Sorry for the tardy comments, but a few things in this changeset caught my eye during our internal Netflix upstream merge review.
Wed, Nov 4
Nov 18 2019
Nov 5 2019
Thanks for the fix @brooks
Oct 14 2019
Oct 8 2019
Oct 2 2019
Sep 24 2019
Aug 12 2019
Jul 11 2019
Mar 28 2019
Feb 25 2019
Feb 7 2019
Agreed and apologies, I misread/miunderstood the code. I also touched base with one of the original CDG authors to sanity check and they agree this change is a good idea.
Feb 5 2019
Suggest moving stailq flush loops out of cdg_cb_destroy() into an inline function, changing smoothing_factor sysctl to a SYSCTL_PROC with custom handler similar to the exp_backoff_scale sysctl, and calling flush function from both cdg_cb_destroy() and sysctl handler when smoothing_factor is set to zero
Actually, we probably need to flush the qdiffmin_q and qdiffmax_q lists in the sample_q_size == 0 branch so that a change back to non-zero smoothing_factor doesn't start operating with stale data.
Thank you for fixing this.
Dec 3 2018
Thanks all for the feedback... I'm a bit rusty on working with ports. Will commit sometime this week with my src commit bit hat on and "review/approved by:" if no further feedback materialises.
Nov 26 2018
Checked with one of the authors. Preference is to reference the Bitbucket URL in pkg-descr if it can only list a single URL.
Full context diff, shuffle variable order and ditch DISTVERSION in favour of a custom variable to hold the commit hash used in the tarball directory name.
Oct 31 2018
@tuexen Any thoughts on the TFO case?
Oct 18 2018
Jul 21 2018
Jul 20 2018
Jun 8 2018
May 17 2018
May 15 2018
May 14 2018
Final commit candidate, rebased against FreeBSD head r333598, and with M_ZERO removed from malloc call.
May 10 2018
newreno_plugleak_v3.diff with getsockopt(2)/setsockopt(2) updated.
@wollman Many thanks for the historical and standards related context - greatly appreciated. I realised that I probably need to update getsockopt(2)/setsockopt(2) as well...
May 9 2018
Still to be tested, but I think something like this would address the leak and change memory allocation to being conditional on need: newreno_plugleak_v1.diff
Mar 19 2018
Feb 7 2018
@jason_eggnet.com I thought about this some more and while there is no doubt that overflow/underflow due to the function's inputs is possible and needs to be remedied, the cause of overflow in your test case is not in fact the time since congestion being too large, but the bogus value of K, which for a wmax of 1460 bytes (i.e. slightly more than 1 MSS) should be 205 per my quick check:
Oh and @jason_eggnet.com , regarding your test code, I structured things the way they are so that you can simply #include <netinet/cc/cc_cubic.h> into your userspace test.c to get access to the various window calculation inlines rather than copy/pasting them.
This fix doesn't make sense to me. If it has been a long time since the last congestion epoch resulting in an overflow in the calculated congestion window, collapsing the window from <something_large> to 1 segment is a terrible idea. There's also no sound reason that cwnd shouldn't be allowed to shrink below 1 segment, and if that causes problems elsewhere, those places should be fixed.
Aug 24 2017
Aug 18 2017
yoda be gone
Aug 17 2017
Update diff post r322614 commit.
Conrad: would you be willing to sanity check this sbuf change for me as well?
Aug 15 2017
Aug 8 2017
Rebase patch against current head and address review feedback.
The off-by-one error was incorrectly attributed to the condition that checks if vsnprintf() was successful at rendering all of the specified content into the sbuf.
Aug 2 2017
Thanks Tom, looking good. Will wait a few days to see if any further feedback materialises.
Jul 28 2017
Jul 27 2017
This looks good barring a couple of nits as noted. Please update tcp(4) and cc_newreno(4) appropriately.
Jul 17 2017
I'm pretty sure this wouldn't compile as proposed. Please remember to build test patches against FreeBSD's svn head branch, as all work always gets comitted to head first before potentially being backported later.
Jul 11 2017
Following up on some discussion held on the fringe of the recent developer summit at BSDCan, what this work is missing is some accompanying documentation to demonstrate the dynamic behaviour of the proposed implementation over some range of relevant network parameters, along with a critique of expected versus measured/observed behaviour. I'm not asking for a full blown academic paper - a stream of consciousness Google-doc with some data, a few X vs time plots and some comments would suffice. Happy to provide guidance if required - you know where to reach me.
May 24 2017
May 4 2017
Apr 7 2017
Mar 19 2017
Apologies for the delay in getting to this.
Feb 20 2017
Feb 17 2017
Nov 17 2016
@kib: You prefer this?
Nov 16 2016
Nov 10 2016
With this patch applied on top of svn head r308477, I built a custom memstick image, wiped the harddrives and reran my build guide steps including creation of the RAIDZ zpool with "-O checksum=skein" option and can confirm the system boots, so although I did not test without this patch applied, I think it's safe to say the patch fixed things given that there have been no other relevant changes in sys/boot between the revision I tested with previously (r307747) and r308477.
To clarify, I did not test prior to this commit, so am not sure if it ever worked. I merely looked up svn log history on sys/boot and this seemed like a plausible culprit assuming there has been a regression.
Nov 9 2016
Is it possible this broke UEFI booting from RAIDZ pools with checksum=skein? If I omit "-O checksum=skein" from my zpool create step everything works great, but with skein checksums, boot1 sees my pool (prints my pool name after "found the following pools" message) but hangs where it should have run loader.efi and then requires a hard reset.
Oct 12 2016
Aug 25 2016
Aug 24 2016
Aug 18 2016
May 18 2016
Apr 29 2016
But why do we need such finely grained control? I don't get it. Either it works or it doesn't. We shouldn't be doing 6675 piecemeal. We should be doing 6675 in full and enabled by default. Providing any level of minutiae beyond enabled/disabled is not only unnecessary but a bad idea IMO.
Why isn't there simply a do_rfc6675 knob that supersedes this and the previously committed work?