[Bug 194453] [dummynet] pipe config bw parameter is limited to 2Gbits per second

2014-10-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194453 --- Comment #7 from Hiren Panchasara --- (In reply to rizzo from comment #6) > (In reply to Hiren Panchasara from comment #5) > > (In reply to boba from comment #4) > > > (In reply to Hiren Panchasara from comment #2) > > > > (In reply to b

[Bug 194453] [dummynet] pipe config bw parameter is limited to 2Gbits per second

2014-10-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194453 ri...@iet.unipi.it changed: What|Removed |Added CC||ri...@iet.unipi.it --- Comment

[Bug 194453] [dummynet] pipe config bw parameter is limited to 2Gbits per second

2014-10-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194453 --- Comment #5 from Hiren Panchasara --- (In reply to boba from comment #4) > (In reply to Hiren Panchasara from comment #2) > > (In reply to boba from comment #0) > > > It's impossible to create "pipe" with bandwidth higher than 2Gbits per

[Bug 194453] [dummynet] pipe config bw parameter is limited to 2Gbits per second

2014-10-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=194453 --- Comment #4 from b...@boba.name --- (In reply to Hiren Panchasara from comment #2) > (In reply to boba from comment #0) > > It's impossible to create "pipe" with bandwidth higher than 2Gbits per > > second. Possible due to "signed" type o

Re: ixgbe(4) spin lock held too long

2014-10-24 Thread John Baldwin
On Thursday, October 23, 2014 02:12:44 PM Jason Wolfe wrote: > On Sat, Oct 18, 2014 at 4:42 AM, John Baldwin wrote: > > On Friday, October 17, 2014 11:32:13 PM Jason Wolfe wrote: > >> Producing 10G of random traffic against a server with this assertion > >> added took about 2 hours to panic, so if

Re: ipfw command freezes system

2014-10-24 Thread Julian Elischer
On 10/23/14, 7:41 AM, javocado wrote: I'm seeing an occasional, recurring problem on my 8.3-RELEASE amd64 systems where when I enter an ipfw rule, the system becomes locked up. For example, when entering a command like this: ipfw add 1 allow ip from x.x.x.x to me or other times with a command

in-kernel nat event log

2014-10-24 Thread k simon
Hi,lists, I would like to use ipfw in-kernel nat or ng_nat to replace my current iptalbe/netfilter nat. Netfilter provides an application called ulogd2 do export netfilter's conntrack record , does FBSD have similar solutions ? Regards Simon ___

Is it needed to install netmap-libpcap in FreeBSD 10.1?

2014-10-24 Thread C. L. Martinez
Hi all, Someone knows if is it needed to install netmap-libpcap in FreeBSD 10.1 or is libpcap already patched to use with netmap in a default FreeBSD 10.1 installation? Thanks. ___ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/l

Re: nd6_timer vs Giant vs locking in general

2014-10-24 Thread Alexander V. Chernikov
On 24.10.2014 09:26, Mateusz Guzik wrote: Hello there, dtrace revealed that the kernel schedules nd6_timer a lot. Not only that, his callout is not mpsafe so the kernel locks Giant which I believe is an oversight. Also the code looks really suspicious as it walks V_in6_ifaddrhead without any lo