Re: callout_drain either broken or man page needs updating

On Thu, 14 Jul 2016 21:21:57 -0700 Hans Petter Selasky wrote > On 07/15/16 05:45, Matthew Macy wrote: > > glebius last commit needs some further re-work. > > Hi, > > Glebius commit needs to be backed out, at least the API change that > changes the

[Bug 194109] [lor] if_lagg rmlock <-> if_addr_lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194109 Kubilay Kocak changed: What|Removed |Added Keywords||needs-qa, patch

Re: refcnt 0 on LLE at boot....

On Thu, 07 Jul 2016 06:36:19 -0700 Larry Rosenman wrote > Thanks for that. I've added myself to the cc list, and a comment about > having 2 vmcore's. > This was introduced by 302350. It broke the return value of callout_{stop,drain}. returning 1 even if

Re: callout_drain either broken or man page needs updating

On 07/15/16 05:45, Matthew Macy wrote: glebius last commit needs some further re-work. Hi, Glebius commit needs to be backed out, at least the API change that changes the return value when calling callout_stop() when the callout is scheduled and being serviced. Simply because there is code

callout_drain either broken or man page needs updating

Upon updating my drm-next branch to the latest -CURRENT callout_drain returning no longer means that the function was in fact pending when it was called. This little bit of code will panic because dwork->wq is NULL, because the callout was _not_ in fact enqueued. So either it's no longer

[Bug 211106] [net][fib][loopback][route] loopback route added only to interface fib, even if net.add_addr_allfibs = 1

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211106 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org

[Bug 194109] [lor] if_lagg rmlock <-> if_addr_lock

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194109 Navdeep Parhar changed: What|Removed |Added Version|CURRENT |11.0-STABLE

Re: panic with tcp timers

On 2016-07-14 12:01, Julien Charbon wrote: Hi, On 6/20/16 11:55 AM, Julien Charbon wrote: On 6/20/16 9:39 AM, Gleb Smirnoff wrote: On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: J> > Comparing stable/10 and head, I see two changes that could J> > affect that: J> > J> > -

Re: panic with tcp timers

Hi, On 6/20/16 11:55 AM, Julien Charbon wrote: > On 6/20/16 9:39 AM, Gleb Smirnoff wrote: >> On Fri, Jun 17, 2016 at 11:27:39AM +0200, Julien Charbon wrote: >> J> > Comparing stable/10 and head, I see two changes that could >> J> > affect that: >> J> > >> J> > - callout_async_drain >> J> > -

proposal: splitting NIC RSS up from stack RSS

Hi, now that 11 is branched and marching on, I'd like to start pushing some more improvements/evolution into the RSS side of things. The short list feedback from people is: * it'd be nice to be able to configure per-device RSS keys on the fly; * it'd be nice to be able to configure per-device

Re: TCP stack lock contention with short-lived connections

Hi, On 6/28/16 12:06 PM, Julien Charbon wrote: > On 12/7/15 4:36 PM, Julien Charbon wrote: >> On 30/05/14 06:12, k simon wrote: >>> Does any plan commit and MFC to the 10-stable ? >> >> I got a bit of interest of having the performance improvements for >> short-lived TCP connections in

[Bug 199096] Kernel panic after some time using mpd (netgraph) and ipfw

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199096 Donald Baud changed: What|Removed |Added CC|

[Bug 210943] Page fault in ip6_setpktopts when syncthing is started with pflog loaded

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210943 Kubilay Kocak changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org

[Bug 211031] [panic] in ng_uncallout when argument is NULL

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211031 Kubilay Kocak changed: What|Removed |Added CC|

[Bug 211031] [panic] in ng_uncallout when argument is NULL

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211031 Kubilay Kocak changed: What|Removed |Added Flags||mfc-stable10?