Committing a new 25G/40G/100G Ethernet Driver

2017-03-23 Thread Somayajulu, David
Hi All, I have a brand new Cavium 25G/40G/100G Ethernet Driver to commit to HEAD. The patch generated using "svn diff" is about 22Mb. Per gnn's advice I have tried to submit the patch via Phabricator at https://reviews.freebsd.org/differential/diff/create/ for review. The file uploads fine but

[Bug 217637] One TCP connection accepted TWO times

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637 --- Comment #79 from Sepherosa Ziehau --- (In reply to Mike Karels from comment #78) Hmm, WAIT1, WAIT2 and CLOSING will transit to TIME_WAIT, so killing them (moving to CLOSED) in the code we talked assassinates TIME_WAIT indirectly. Or a

[Bug 217637] One TCP connection accepted TWO times

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217637 --- Comment #78 from Mike Karels --- (In reply to Sepherosa Ziehau from comment #77) I don't think it is similar, although I haven't thought it through in great detail. For starters, there is no TIME_WAIT to assassinate. I don't see how

[Bug 217920] [PATCH] ipfilter discard bytes - 3072 instead of 1024

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217920 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org -- You are

[Bug 218004] sys/dev/sfxge/common/efx_mcdi.c: PVS-Studio: Unreachable code detected (CWE-561)

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218004 Mark Linimon changed: What|Removed |Added Summary|sys/dev/sfxge/common/efx_mc |sys/dev/sfxge/common/efx_mc

[Bug 218005] sys/netinet/sctp_pcb.c: PVS-Studio: Unreachable code detected (CWE-561)

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218005 Mark Linimon changed: What|Removed |Added Assignee|freebsd-b...@freebsd.org|freebsd-net@FreeBSD.org

[Bug 218041] sys/dev/e1000/if_em.c: PVS-Studio: V646: possible 'else' keyword missing

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=218041 Mark Linimon changed: What|Removed |Added Summary|sys/dev/e1000/if_em.c: |sys/dev/e1000/if_em.c:

Re: if_epair altq support problem

2017-03-23 Thread Ermal Luçi
On Thu, Mar 23, 2017 at 12:16 PM, Özkan KIRIK wrote: > Ermal thank you again, > It compiles but pf still says that "pfctl: epair0b: driver does not > support altq" > :/ > The only way to get that error is by not applying the patch properly :) > > On Thu, Mar 23, 2017 at 9:46 PM, Ermal Luçi wr

Re: if_epair altq support problem

2017-03-23 Thread Özkan KIRIK
Ermal thank you again, It compiles but pf still says that "pfctl: epair0b: driver does not support altq" :/ On Thu, Mar 23, 2017 at 9:46 PM, Ermal Luçi wrote: > > On Thu, Mar 23, 2017 at 11:06 AM, Özkan KIRIK > wrote: > >> Thank you, I'm waiting for 10.3 fix :) >> have a nice day >> > > > This

Re: if_epair altq support problem

2017-03-23 Thread Ermal Luçi
On Thu, Mar 23, 2017 at 11:06 AM, Özkan KIRIK wrote: > Thank you, I'm waiting for 10.3 fix :) > have a nice day > This should work for 10.3++ diff --git a/sys/net/if_epair.c b/sys/net/if_epair.c index 540f06c..d028a95 100644 --- a/sys/net/if_epair.c +++ b/sys/net/if_epair.c @@ -829,7 +829,8 @

Re: cxgbe netmap promiscuous mode?

2017-03-23 Thread Navdeep Parhar
Your netmap application should be using the 'vcxl' interface, not the cxl interface. Even though they share a physical port they have different MAC addresses and are totally autonomous. The peer should use the vcxl interface's MAC if it wants to reach the netmap application. Do you have the pani

Re: cxgbe netmap promiscuous mode?

2017-03-23 Thread Vincenzo Maffione
Hi, You could try to use netmap in emulated mode (sysctl dev.netmap.admode=2). If this works, at least you know that the problem is in the cxgbe netmap support and not in the netmap core itself. Cheers, Vincenzo 2017-03-23 14:00 GMT+01:00 Joe Jones : > Hello, > > We have a T520-SO and have m

Re: if_epair altq support problem

2017-03-23 Thread Özkan KIRIK
Thank you, I'm waiting for 10.3 fix :) have a nice day On Wed, Mar 22, 2017 at 11:44 PM, Ermal Luçi wrote: > > On Wed, Mar 22, 2017 at 10:50 AM, Özkan KIRIK > wrote: > >> Sorry, I mistested on 10.3RELENG. >> it works on 11 RELENG, But at 10.3RELENG it throws >> >> /usr/src/sys/modules/if_epair

[Bug 211643] ixgbe(4) does not reliably bring up 10G links with ZyXEL XS1920 switches

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211643 --- Comment #3 from Kurt Jaeger --- Ticket with supermicro: SM1703233787 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd.org mailing list https:

Re: LLE reference leak in the L2 cache

2017-03-23 Thread Andrey V. Elsukov
On 20.03.2017 03:46, Mike Karels wrote: > The context has gotten messy here, so I’m going to break down and top-post. > > I started review https://reviews.freebsd.org/D10059 with a fix for the > reference-count leak. > It changes the semantics so only routes within an in_pcb automatically > do L2

cxgbe netmap promiscuous mode?

2017-03-23 Thread Joe Jones
Hello, We have a T520-SO and have made a new install of 11.0, to begin with the box would panic every time we tried to switch the card into netmap mode. So we recompiled the kernel with netmap removed, then compiled the netmap kernel module from github, as this in our experience generally lea

[Bug 211643] ixgbe(4) does not reliably bring up 10G links with ZyXEL XS1920 switches

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211643 --- Comment #2 from Kurt Jaeger --- Ticket at Ubiquity https://help.ubnt.com/hc/requests/682423 -- You are receiving this mail because: You are the assignee for the bug. ___ freebsd-net@freebsd

[Bug 211643] ixgbe(4) does not reliably bring up 10G links with ZyXEL XS1920 switches

2017-03-23 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211643 Kurt Jaeger changed: What|Removed |Added CC||p...@freebsd.org --- Comment #1 from