em driver input errors

Dmitriy Zamuraev gigabyte.tmn at gmail.com
Thu Aug 20 11:58:28 UTC 2009


Hello Alex,

> SCHED_ULE, HZ=1000:
I use this too

>> > From the output of "netstat -nI em0 -w 5":
>> maybe mistake, did you meen "netstat -w5 em0" ?
> Nope, exactly as in my mail, "netstat -nI em0 -w 5".  It does take 5 
> seconds to produce meaningful output.
hmm, just comments:
-n    Show network addresses and ports as numbers.
-l    Shows listen sockets
-nl with -w is wrong parameters.

> I have PPPoE concenrator based on S3000AHV motherboard with
> Core2Quad 6600 and four (to load all cores in CPU) Intel
> PCI-E x1 and PCI-E x4 NIC's
> My load:
> ...
> Pretty impressive figures.  And "netstat -ni" shows 0 errors on all cards?
Not exactly zero, but for uptime 155 days it seems to be ok.
bras1 [/usr/home/dm]# netstat -i|grep em
em0    1500 <Link#1>      00:15:17:71:f8:52 2457503820 20175 2096211799 
0     0
em1    1500 <Link#2>      00:15:17:71:f8:52 1084492221 11188 909418060     0 
0
em2    1500 <Link#3>      00:15:17:71:f8:52 4212941427 29566 3500442287 
0     0
em3    1500 <Link#4>      00:15:17:71:f8:52 2143321197     0 1878792786 
0     0
This counters was made by UDP flood, when dummynet can't process all packets 
and
swi:net loads one core up to 100%. Yes, the dummynet on this machine, its 
bad idea but it's
working stable. (After this incident the switches now control the flood 
attack)
NOTE: the MAC is equal because i use if_lagg(4) for this interfaces for load 
all cores in CPU

>> I think it depends by motherbord, what full hardware specification are 
>> you using? with chips names
> The machine is a Dell PowerEdge 2850.  According to its specs, the chipset 
> is Intel E7520.
> Two 64-bit Xeon processors at 3.20GHz, 4 GB RAM.
For you bandwidth this server must work fine.
Check the UDP/ICMP or other flood on em0 when errors appear.
What kind of device at the end of em0 copper cable?
If this a manageable switch, and supports tools - try to investigate what 
happens when errors appear.



More information about the freebsd-net mailing list