Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time
On Wed, May 11, 2016 at 10:46:01PM -0700, Yuri wrote: > On 05/08/2016 02:33, YongHyeon PYUN wrote: > >msk(4) will try to use MSI unless not configured to do so the IRQ > >wouldn't be shared with other devices. If msk(4) is using MSI you > >should see a high irq number greater than or equal to 256 in vmstat > >output. Given that you're seeing issues with MSI, try disabling > >MSI for msk(4). Add the following tunable to /boot/loader.conf and > >reboot. > > > >hw.msk.msi_disable="1" > > For some reason hw.msk.msi_disable isn't found: > # sysctl hw.msk.msi_disable=1 > sysctl: unknown oid 'hw.msk.msi_disable' > even though it is defined in sys/dev/msk/if_msk.c and if_msk module is > loaded. hw.msk.msi_disable is a loader tunable so you can't check it with sysctl(8). Add the tunable to boot/loader.conf to take it effect. See loader.conf(5) for more information. ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Marvell Yukon (msk) network card causes the "sticky mouse" problem: mouse stops for extended periods of time
On 05/08/2016 02:33, YongHyeon PYUN wrote: msk(4) will try to use MSI unless not configured to do so the IRQ wouldn't be shared with other devices. If msk(4) is using MSI you should see a high irq number greater than or equal to 256 in vmstat output. Given that you're seeing issues with MSI, try disabling MSI for msk(4). Add the following tunable to /boot/loader.conf and reboot. hw.msk.msi_disable="1" For some reason hw.msk.msi_disable isn't found: # sysctl hw.msk.msi_disable=1 sysctl: unknown oid 'hw.msk.msi_disable' even though it is defined in sys/dev/msk/if_msk.c and if_msk module is loaded. Yuri ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
ipfw tcpack won't match a given ack #
Hello, This rule: 1 0 0 deny log logamount 1000 tcp from any to 100.100.224.66 tcpack 2 Won't match this attack pattern below. Is tcpack supposed to match it? FreeBSD 10.2-STABLE #0 r292035M Can I try to match it with some other tool? I tried pf but looks like it won't filter (look into) this kind of information. Thank you. 16:20:47.583871 IP 200.200.67.221.51352 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584022 IP 200.200.67.221.51354 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584324 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584475 IP 200.200.67.221.51364 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584718 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.584868 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585169 IP 200.200.67.221.51353 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585557 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585623 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.585801 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586081 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586226 IP 200.200.67.221.51354 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586649 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.586652 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.587124 IP 200.200.67.221.51355 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 16:20:47.587129 IP 200.200.67.221.51351 > 100.100.224.66.80: Flags [.], ack 2, win 0, length 0 ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Questions on iflib
On Wed, 11 May 2016 11:27:20 -0700 "K. Macy" wrote > On Wed, May 11, 2016 at 7:56 AM, Chris H wrote: > > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara > > wrote > > > >> + Kip, Scott. > >> > >> On 05/10/16 at 04:46P, David Somayajulu wrote: > >> > Hi All, > >> > I have a couple of questions on iflib : > >> > > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, will > >> > it make it into FreeBSD11 release ? > >> > >> Yes. The library itself (without any drivers) is being prepared for > >> committing to CURRENT. > > This is intended to be optional. Right? > > The name Iflib is short for iflnet library. A driver has to be > programmed to it. It will always be possible to program directly to > ifnet, but henceforth it will be frowned upon when not absolutely > necessary. As iflib will ultimately make the driver more performant > and more maintainable. As a counterexample, the Chelsio driver has to > manage multiple ports on a single device and handle synchronization > with upper level protocols. It's also extremely well optimized > already. I don't know of any other network driver that can justify > opting out for one of those reasons, much less both. > > -M No. Makes perfect sense. I'm afraid I mis-guessed it's intent. Sorry for the noise, and thanks for taking the time to reply. :) --Chris -- ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Questions on iflib
On Wed, May 11, 2016 at 7:56 AM, Chris H wrote: > On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara > wrote > >> + Kip, Scott. >> >> On 05/10/16 at 04:46P, David Somayajulu wrote: >> > Hi All, >> > I have a couple of questions on iflib : >> > >> > 1. Are there plans to incorporate iflib into CURRENT. If yes, will it >> > make it into FreeBSD11 release ? >> >> Yes. The library itself (without any drivers) is being prepared for >> committing to CURRENT. > This is intended to be optional. Right? The name Iflib is short for iflnet library. A driver has to be programmed to it. It will always be possible to program directly to ifnet, but henceforth it will be frowned upon when not absolutely necessary. As iflib will ultimately make the driver more performant and more maintainable. As a counterexample, the Chelsio driver has to manage multiple ports on a single device and handle synchronization with upper level protocols. It's also extremely well optimized already. I don't know of any other network driver that can justify opting out for one of those reasons, much less both. -M ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
Re: Questions on iflib
On Tue, 10 May 2016 10:25:24 -0700 hiren panchasara wrote > + Kip, Scott. > > On 05/10/16 at 04:46P, David Somayajulu wrote: > > Hi All, > > I have a couple of questions on iflib : > > > > 1. Are there plans to incorporate iflib into CURRENT. If yes, will it > > make it into FreeBSD11 release ? > > Yes. The library itself (without any drivers) is being prepared for > committing to CURRENT. This is intended to be optional. Right? > > > > > 2. Where can I get the latest patch of iflib for FreeBSD_CURRENT ? > > Kip or Scott may provide more info. > > Cheers, > Hiren --Chris ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
