Fix the manpage to document that the gateway parameter is
optional for most route subcommands.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 16 2018
Feb 10 2018
Jan 29 2018
Jan 23 2018
Jan 22 2018
Add comment explaining generation increment
In D13988#293614, @karels wrote:Could this use the new invalidate macro?
Jan 19 2018
NULL-out rte after route cache is invalidated
Dec 14 2017
Dec 13 2017
In D13417#281628, @ae wrote: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
In D11560#239289, @hselasky wrote:Hi,
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?
--HPS
Jul 11 2017
Jun 27 2017
May 29 2017
@kmacy I have not. We probably have an equivalent fix committed locally @ $WORK but it might be tied too closely to the high-precision timestamp work to easily extract.
May 24 2017
May 3 2017
In D10535#218388, @sbruno wrote:Maybe you've seen something that requires this lock acquisition in your testing. Can you explain why we need to acquire this lock here?
Apr 28 2017
Apr 5 2017
Apr 3 2017
Add the locking mentioned the description but omitted from the
actual revision.
I'm not sure what we want to do with this fix given the imminent iflib conversion, but at least this should go into stable branches.
Mar 22 2017
Obsoleted by gleb's User/Kernel KPI fixes
Feb 23 2017
Feb 18 2017
Feb 17 2017
Feb 16 2017
Feb 15 2017
In D9465#198397, @pkelsey wrote:I realize the issue there is exposure of a type definition to userland, but a related question is - what exactly is the userland-ABI property we are trying to maintain here? Are we just trying to keep this struct the same size and layout under all kernel configuration option selections and feature evolutions for a given machine type? Or are we also trying to keep it the same size and layout across different machine types (or at the very least a single pair of relevant machine types)? For example, is the #ifdef_LP64 really necessary in the TCPPCAP section?
Feb 11 2017
- fixup! Don't zero out srtt after excess retransmits
Feb 9 2017
See this ML post for a detailed description of the problem:
https://lists.freebsd.org/pipermail/freebsd-current/2013-January/039261.html
Feb 7 2017
Feb 6 2017
Jan 20 2017
Dec 9 2016
Dec 2 2016
Dec 1 2016
Nov 30 2016
Ensure we don't walk off the end of the ring
Nov 26 2016
Nov 23 2016
Nov 18 2016
Nov 17 2016
Nov 12 2016
Nov 11 2016
--git-dir is unreliable, so use -C $git_repo instead
Similar fix is needed in importgit
This is not the correct fix. The bug lies in a higher layer; the stack must never call into the ifnet layer with the if_addr_lock already held. I see how to fix the upper layer, so I'll take that.