Is this still alive? As ECN has become more interesting recently, something like this is probably needed for RFC3168 ECN flows.
Also, forgive my ignorance, but can the LRO code add some side-band information to the upstream - e.g. number of packets coalesced, or number of CE marks observed? This would be very relevant in context of Accurate ECN. Where for RFC3168 it is sufficience that any segment marked as CE to appear in the final header, for AccECN the actual number of the CE marks, and also the number of coalesced packets would be relevant, to arrive at an appropriate alpha (reduction) value.
By just moving any number of CE marks to a single, the AccECN CC reaction would be more strong, shedding more bandwidth than appropriate...
Jan 24 2020
Jan 20 2020
Jan 10 2020
Jan 9 2020
Jan 7 2020
Jan 2 2020
Dec 21 2019
Dec 3 2019
Nov 26 2019
Do you happen to have a test case for this? We don't have any ND6 regression tests at the moment. :(
Oct 30 2019
Oct 23 2019
Oct 8 2019
I suspect that means that your BIOS pre-allocated enough bus numbers to the bridge to account for the VFs. Perhaps we should add a pcib method that recursively checks that a contiguous range of bus numbers is assigned to the bridge?
Oct 1 2019
Aug 27 2019
Oct 4 2018
Sep 19 2018
Jun 12 2018
@rstone do you think you might be able to share the work that you or Jeff did on the frontend to adaptively lower the minRTO if the pipe was full?
May 17 2018
I do not see such code in mlx4_en_rx.c. Could you point it out, please ?
May 16 2018
Well, from my reading, your patch and this patch are quite similar, but this review provides two interesting optimizations.
- Use page-size fragments if MTU >= PAGE_SIZE, already discussed on lists for mlx5.
- Keep around mbufs and memory for unused fragments, if the received packed was shorter than MTU.
If these changes are transplanted into your patch, I believe the things start look almost identical. I want to confirm my understanding with Ryan.
May 7 2018
The message that I got at BSDCan last year is that they wanted to see at least a full IETF draft before these changes could be merged in, which is why my work on it stalled. Has people's position on this changed?
FWIW, I had a short email conversation with the writers of that draft about a year ago and they went radio silent pretty quickly. I assumed that they weren't working on it anymore.
Mar 19 2018
Mar 14 2018
Where is route.subr? And where did ipv4_move_subnet_route come from? I think you used the wrong base revision to generate the review.
Move non-fib test into separate test file
Mar 8 2018
Mar 7 2018
I've written some unit tests that covering these cases here:
Mar 5 2018
I don't think that this conversation is going to go anywhere productive. Do you have specific technical objection to raise about this change?
Care to elaborate what are you trying to achieve by moving subnet route between interfaces?
Uploaded the wrong test to this review; fixed now
Move route(8) tests to their own atf test file
In any case, even if the use-case is weird, the current behaviour is clearly buggy and needs to be fixed in some way.
Well, I guess so. But original configuration may be supposed to be "buggy" too (read: not supported). What if you use /16 mask for single interface only and assign IP from the same prefix to other interfaces using /32 mask?
Mar 1 2018
And you do you insist in doing things manually while moving IP (first route change, then reassign IP) instead of just allowing system do all housekeeping for you by reassigning IP first?
Add ATF test cases for IPv4/IPv6 subnet route migration
The fibs must actually exist. Set net.fibs=6 in /boot/loader.conf and reboot. Also, are you sure you need so many? I don't think there are any tests there that require more than two.
In tests/sys/netinet/fibs_test.sh there are some ATF tests that check this kind of functionality. They do it on separate FIBs so they won't upset the system running the tests, and they use tap(4) and/or epair(4) interfaces. You should be able to copy one of those to create a regression test for this problem.
Feb 28 2018
Check for NULL pointers
Feb 21 2018
Feb 16 2018
How it supposed to work for RADIX_MPATH case? I know RADIX_MPATH is currently broken, but anyway...
Clarify manpage update as per rgrimes' suggestion
Fix the manpage to document that the gateway parameter is
optional for most route subcommands.
Feb 10 2018
Jan 29 2018
Jan 23 2018
Jan 22 2018
Add comment explaining generation increment
Jan 19 2018
NULL-out rte after route cache is invalidated
Dec 14 2017
Dec 13 2017
It would be nice if you describe why this leak happens, i.e. where leaked reference was acquired.
Dec 7 2017
Nov 17 2017
Oct 24 2017
Oct 23 2017
Oct 16 2017
Oct 11 2017
Sep 22 2017
Sep 12 2017
Aug 15 2017
Aug 4 2017
Aug 2 2017
Jul 31 2017
Jul 20 2017
Jul 13 2017
Jul 12 2017
Don't pull the "old behaviour" into the driver. You should use a linked list of mbufs and load that instead of the mlx4_en_frag_info structure now we are using busdma!
There is a better way to implement this. Can Mellanox take over this issue?