Re: UDP on FreeBSD

On Wed, Mar 30, 2011 at 3:43 PM, Kyungsoo Lee wrote: > Hi All, > > I want to check UDP on FreeBSD. > > I am using IPERF on FreeBSD for wireless testing with Proxim 8470 FC PCMCIA > card on IBM T42 and T61. > > When I'm transmitting data from FreeBSD to FreeBSD or CentOS using Iperf > with -u -b 10

net80211 and interface requests

Hello, This list has helped me before so I'll email again with the hopes that somebody has an answer. All is working well with my project, however for the life of me I cannot get the interface to inject the raw frames faster than 11mbps. I'm following the example given in /usr/src/tools/tools/ne

Re: Kernel memory corruption(?) with age(4)

On Wed, Mar 30, 2011 at 09:50:12PM +0200, Yamagi Burmeister wrote: > On Wed, 30 Mar 2011, YongHyeon PYUN wrote: > > >On Wed, Mar 30, 2011 at 04:22:23PM +0200, Yamagi Burmeister wrote: > > > >>All for boxes are unstable if the Attansic NIC is in use, no one of them > >>survived more than 60 minutes

Re: Kernel memory corruption(?) with age(4)

On Wed, 30 Mar 2011, YongHyeon PYUN wrote: On Wed, Mar 30, 2011 at 04:22:23PM +0200, Yamagi Burmeister wrote: All for boxes are unstable if the Attansic NIC is in use, no one of them survived more than 60 minutes of ~20mb/s network traffic. I managed to get some coredumps and extracted the bac

UDP on FreeBSD

Hi All, I want to check UDP on FreeBSD. I am using IPERF on FreeBSD for wireless testing with Proxim 8470 FC PCMCIA card on IBM T42 and T61. When I'm transmitting data from FreeBSD to FreeBSD or CentOS using Iperf with -u -b 100M on iperf, they had lost lots of packets. Sniffer near the two node

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Read the code in HEAD, em_local_timer() has a test of ALL the rx queues and will schedule a task that refreshes mbufs if they are empty. This has exactly the same effect as checking for some interrupt cause, a cause that is not available when using MSIX on 82574, but this approach works for everyth

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Hi, Maybe you're right. OK, let's return default hw.igb.rxd to 256. It seems to be enough for stable work and driver is used less memory. BTW, on the man page igb(4) still written that hw.igb.rxd equals to 256 by default. -- Andrey Zonov 30.03.2011 18:33, Arnaud Lacombe пишет: Hi, On Wed

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Hi, On Wed, Mar 30, 2011 at 1:12 PM, Jack Vogel wrote: > The code that got put in the driver has a response to this "unrecoverable > situation", you've flamed me and the code, but you've not demonstrated it > does not work. > I did, in "Message-ID: ". If you want to talk code, please tell me wher

Re: igb(4) won't start with "igb0: Could not setup receive structures"

On Wed, Mar 30, 2011 at 1:10 PM, Doug Barton wrote: > On 3/30/2011 10:06 AM, Arnaud Lacombe wrote: >> >> No. We are taking about exceptional recoverable situation not handled >> by the software, it should not bring the complete system down. If >> you're swapping code has defect, you do not tell on

Re: Kernel memory corruption(?) with age(4)

On Wed, Mar 30, 2011 at 04:22:23PM +0200, Yamagi Burmeister wrote: > Hi, > I recently got four about two years old Asus M3A-H/HDMI mainboards with > an integrated Attansic L2 ethernet controller. This NIC is supported by > age(4) and recognized by freebsd: > > > > age0: >mem 0xfeac0

Re: bge(4) on RELENG_8 mbuf cluster starvation

On Wed, Mar 30, 2011 at 7:10 PM, YongHyeon PYUN wrote: > On Wed, Mar 30, 2011 at 05:55:47PM +0200, Vlad Galu wrote: > > On Sun, Mar 13, 2011 at 2:16 AM, YongHyeon PYUN > wrote: > > > > > On Sat, Mar 12, 2011 at 09:17:28PM +0100, Vlad Galu wrote: > > > > On Sat, Mar 12, 2011 at 8:53 PM, Arnaud La

Re: igb(4) won't start with "igb0: Could not setup receive structures"

On Wed, Mar 30, 2011 at 10:06 AM, Arnaud Lacombe wrote: > Hi, > > On Wed, Mar 30, 2011 at 12:44 PM, Doug Barton wrote: > > On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: > >> > >> Hi, > >> > >> On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton wrote: > > > >> The only things I've been able to get from

Re: bge(4) on RELENG_8 mbuf cluster starvation

On Wed, Mar 30, 2011 at 05:55:47PM +0200, Vlad Galu wrote: > On Sun, Mar 13, 2011 at 2:16 AM, YongHyeon PYUN wrote: > > > On Sat, Mar 12, 2011 at 09:17:28PM +0100, Vlad Galu wrote: > > > On Sat, Mar 12, 2011 at 8:53 PM, Arnaud Lacombe > > wrote: > > > > > > > Hi, > > > > > > > > On Sat, Mar 12,

Re: igb(4) won't start with "igb0: Could not setup receive structures"

On 3/30/2011 10:06 AM, Arnaud Lacombe wrote: No. We are taking about exceptional recoverable situation not handled by the software, it should not bring the complete system down. If you're swapping code has defect, you do not tell one to buy more RAM not to trigger the defective code, you fix the

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Hi, On Wed, Mar 30, 2011 at 12:44 PM, Doug Barton wrote: > On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: >> >> Hi, >> >> On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton  wrote: > >> The only things I've been able to get from Jack is "We, at Intel, test >> em(4) at 256k nmbclusters. We do not have prob

Re: igb(4) won't start with "igb0: Could not setup receive structures"

On 3/30/2011 7:19 AM, Arnaud Lacombe wrote: Hi, On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton wrote: The only things I've been able to get from Jack is "We, at Intel, test em(4) at 256k nmbclusters. We do not have problem. If you have problem, raise nmbcluster.". 256k nmbcluster in my environ

Re: bge(4) on RELENG_8 mbuf cluster starvation

On Sun, Mar 13, 2011 at 2:16 AM, YongHyeon PYUN wrote: > On Sat, Mar 12, 2011 at 09:17:28PM +0100, Vlad Galu wrote: > > On Sat, Mar 12, 2011 at 8:53 PM, Arnaud Lacombe > wrote: > > > > > Hi, > > > > > > On Sat, Mar 12, 2011 at 4:03 AM, Vlad Galu wrote: > > > > Hi folks, > > > > > > > > On a fai

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Hi, On Wed, Mar 30, 2011 at 1:58 AM, Andrey Zonov wrote: > My point is if you're using machine with 8 CPUs than maxusers/clusters/9k > mbufs should have been increased by system, because on this machine minimum > 2Gb memory is available. > I am doubtful that the number of CPU[0] or number of user

Kernel memory corruption(?) with age(4)

Hi, I recently got four about two years old Asus M3A-H/HDMI mainboards with an integrated Attansic L2 ethernet controller. This NIC is supported by age(4) and recognized by freebsd: age0: mem 0xfeac-0xfeaf irq 18 at device 0.0 on pci2 age0: 1280 Tx FIFO, 2364 Rx FIFO age0: U

Re: igb(4) won't start with "igb0: Could not setup receive structures"

Hi, On Wed, Mar 30, 2011 at 1:11 AM, Doug Barton wrote: > On 03/29/2011 22:07, Arnaud Lacombe wrote: >> >> ... or maintain internal changes to the driver to make it not that memory >> hungry/behave well under memory pressure, especially on system where >> memory_is_  a constraint. > > If you come

Re: kern/154006: [tcp] [patch] tcp "window probe" bug on 64bit

Synopsis: [tcp] [patch] tcp "window probe" bug on 64bit State-Changed-From-To: open->patched State-Changed-By: jhb State-Changed-When: Wed Mar 30 12:38:33 UTC 2011 State-Changed-Why: Fix committed to HEAD. Responsible-Changed-From-To: freebsd-net->jhb Responsible-Changed-By: jhb Responsible-Cha

Re: The tale of a TCP bug

On Monday, March 28, 2011 2:38:10 pm Stefan `Sec` Zehl wrote: > Hi, > > On Mon, Mar 28, 2011 at 14:23 -0400, John Baldwin wrote: > > > > No, this is not really right. Your patch from your blog is the best > > fix actually. The reason we want to let 'win' be larger than > > TCP_MAXWIN is that if