problems with em(4) since update to driver 7.2.2

[Arnaud Lacombe]

Hi Jack,

On Tue, May 3, 2011 at 6:00 PM, Jack Vogel <jfvogel at gmail.com> wrote:
> It has nothing to do with load, it has to do with the prerequisites to init
> your interfaces.
> The amount you need is fixed, it doesn't vary with load. Every RX descriptor
> needs one,
> so its simple math, number-of-interfaces X number-of-queues X size of the
> ring.
>
I guess the question is more: why would I need N*M (M > 1) nmbclusters
with driver version X when driver version X-1 worked perfectly fine,
from my daily-average-user point of view, with N nmbclusters ?

A more rude version might be "Why the frak my network adapter stopped
working with the default setting ?" :)

 - Arnaud

> If you have other network interfaces beside Intel they also consume mbufs
> remember.
>
> Jack
>
>
>
> On Tue, May 3, 2011 at 2:50 PM, Michael Schmiedgen <schmiedgen at gmx.net>wrote:
>
>> On 03.05.2011 23:24, Jack Vogel wrote:
>>
>>> If you get the setup receive structures fail, then increase the
>>> nmbclusters.
>>>
>>> If you use standard MTU then what you need are mbufs, and standard size
>>> clusters (2K).
>>> Only when you use jumbo frames will you need larger.
>>>
>>> You must configure enough, its that simple.
>>>
>>
>> I doubled the nmbclusters as well. But nothing happened.
>>
>> I have no load on this machine and nothing special
>> configured.
>>
>> Thanks,
>>  Michael
>>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>