Re: kern/171520: [alc] alc network driver + tso + vlan does not work.

2012-10-21 Thread YongHyeon PYUN
On Mon, Oct 22, 2012 at 10:15:28AM +0600, Nikolay Nevzorov wrote: > 2012/10/22 Eugene Grosbein > > > 22.10.2012 10:55, Nikolay Nevzorov пишет: > > > I can make clean test. > > > > > > What do you mean by clean: > > > reboot with disable mpd (and so will be not enabled kernel NAT in > > system) or

Re: kern/171520: [alc] alc network driver + tso + vlan does not work.

2012-10-21 Thread Eugene Grosbein
22.10.2012 11:09, Nikolay Nevzorov пишет: > Any traffic throuhg NAT does not cause problems. And any routed traffic so on. > > Problem only with traffic that generated on host with alc0, because host > generate packets much more bigger than MTU (about 2300 bytes per packet with > MTU 1500), a se

Re: kern/171520: [alc] alc network driver + tso + vlan does not work.

2012-10-21 Thread Nikolay Nevzorov
2012/10/22 Eugene Grosbein > 22.10.2012 10:55, Nikolay Nevzorov пишет: > > I can make clean test. > > > > What do you mean by clean: > > reboot with disable mpd (and so will be not enabled kernel NAT in > system) or remove LIBALIAS from kernel too? > > You need not reboot or disable mpd. Just mak

Re: ixgbe & if_igb RX ring locking

2012-10-21 Thread Ryan Stone
On Sun, Oct 21, 2012 at 2:21 PM, Alexander V. Chernikov wrote: >> ix:rx -> udp is also fairly obvious (here's one backtrace): > The same question, where "udp" -> "ix:rx" can happen ? It can't happen directly as far as I can tell. But to trigger a deadlock, "all" that has to happen is that a thr

Re: kern/172895: [ixgb] [ixgbe] do not properly determine link-state

2012-10-21 Thread linimon
Old Synopsis: [ixgb,ixgbe] does not properly determine link-state for New Synopsis: [ixgb] [ixgbe] do not properly determine link-state Responsible-Changed-From-To: freebsd-bugs->freebsd-net Responsible-Changed-By: linimon Responsible-Changed-When: Mon Oct 22 01:24:47 UTC 2012 Responsible-Changed-

Re: [RFC] Enabling IPFIREWALL_FORWARD in run-time

2012-10-21 Thread Julian Elischer
On 10/19/12 4:25 AM, Andrey V. Elsukov wrote: Hi All, Many years ago i have already proposed this feature, but at that time several people were against, because as they said, it could affect performance. Now, when we have high speed network adapters, SMP kernel and network stack, several locks a

Re: VIMAGE crashes on 9.x with hotplug net80211 devices

2012-10-21 Thread Adrian Chadd
On 21 October 2012 14:22, Marko Zec wrote: >> Right; would that be at the net80211 side, or something higher up (eg >> at device_attach, which gets called from the cardbus/pci bridge >> enumeration code.) > > As high as it gets - if you get lucky, as a side effect you might even fix > similar iss

Re: VIMAGE crashes on 9.x with hotplug net80211 devices

2012-10-21 Thread Marko Zec
On Sunday 21 October 2012 21:50:21 Adrian Chadd wrote: > On 21 October 2012 12:36, Marko Zec wrote: > > The right approach would be to do a single CURVNET_SET(vnet0) / > > CURVNET_RESTORE() somewhere near the root of the call graph being > > triggered by the hotplug attach event. Not having any h

Re: VIMAGE crashes on 9.x with hotplug net80211 devices

2012-10-21 Thread Adrian Chadd
On 21 October 2012 12:36, Marko Zec wrote: > The right approach would be to do a single CURVNET_SET(vnet0) / > CURVNET_RESTORE() somewhere near the root of the call graph being triggered > by the hotplug attach event. Not having any hotpluggable hardware at hand > I cannot be more specific where

Re: VIMAGE crashes on 9.x with hotplug net80211 devices

2012-10-21 Thread Marko Zec
On Sunday 21 October 2012 21:04:41 Adrian Chadd wrote: > Hi all, > > I have some crashes in the VIMAGE code on releng_9. Specifically, when > I enable VIMAGE and then hotplug some cardbus ath(4) NICs. > > The panics are dereferencing the V_ ifindex and related fields. > > If I start adding CURVNET_

VIMAGE crashes on 9.x with hotplug net80211 devices

2012-10-21 Thread Adrian Chadd
Hi all, I have some crashes in the VIMAGE code on releng_9. Specifically, when I enable VIMAGE and then hotplug some cardbus ath(4) NICs. The panics are dereferencing the V_ ifindex and related fields. If I start adding CURVNET_SET(vnet0) and CURVNET_RESTORE() around the ifnet calls (attach, det

Re: ixgbe & if_igb RX ring locking

2012-10-21 Thread Alexander V. Chernikov
On 16.10.2012 17:20, Ryan Stone wrote: On Tue, Oct 16, 2012 at 8:47 AM, Gleb Smirnoff wrote: Can you please provide hints how can SIOCADDMULTI lead to obtaining RX lock in the stock driver? It doesn't. But it does acquire the core lock, and the core lock is acquired before the RX lock (in ix

Re: [RFC] Enabling IPFIREWALL_FORWARD in run-time

2012-10-21 Thread Eitan Adler
On 19 October 2012 07:25, Andrey V. Elsukov wrote: > Hi All, > > Many years ago i have already proposed this feature, but at that time > several people were against, because as they said, it could affect > performance. Now, when we have high speed network adapters, SMP kernel > and network stack,

Re: kern/171520: [alc] alc network driver + tso + vlan does not work.

2012-10-21 Thread Eugene Grosbein
21.10.2012 12:19, Nikolay Nevzorov wrote: > There is libalias in my kernel config, and i use it on ng0, not on alc0. And > libalias used not in ipfw - netgraph with it builded by mpd. Anyway this bug? AFAIK, mpd uses ng_nat(4) that is based on kernel version of libalias, the same as ipfw nat i