Hi Azeem!
I have a PC with an onboard NVIDIA GbE NIC, an Intel 82540OEM NIC and an
Intel 82545EM NIC in PCI slots.
If it's in a PCI slot, could you please have a look in dmesg at the point where
the e1000 driver module loads and could you check which kind of PCI interface
the driver uses?
Hello Frank,
Thank you for replying.
Yes indeed, the Intel NIC is operating at 33MHz and 32 bit mode. From lspci
-v I had mistakenly concluded that the NIC was operating at 66MHz. It turns out
that the reason I had very high throughput earlier with the onboard NIC is that
the onboard
Hi All,
we are trying to change the igb driver to support UDP segmentation in linux.
the chipset we use is 82576.
as it appears the stack supports it but the function igb_tso_adv
assumes its a tcp message and set the context with TCP parameters.
we want to change the code to support UDP. however
http://admaster.heyos.com/core/newsletter_click.asp?idutente=9000
A breve sarà attivo il servizio newsletter di ConsoleWorld
javascript:void(0);/*1240103102869*/
!!
Ogni settimana riceverete le ultime notizie dal forum, per restare
sempre aggiornati sulle novità della Community!!
e1000e: write protect ICHx NVM to prevent malicious write/erase
no, doesn't apply to this hardware, as it is not ICH (integrated LOM) it
is a standalone 82571 with an actual discreet eeprom chip per port.
to include our modules as well in order to find out who is overwriting
memory?
After experimenting with kexec with the last merges after 2.6.29, I've
had some problems when probing e100. It would not read the eeprom. After
some bisects, I realized this has been like that since forever (at least
2.6.18). The problem is that shutdown is doing the same thing that
suspend does
That make it safer? My poor boy has talked it firmly, and
the youth obeyed. Wingrave led the.
How to Talk to Yoour Husband About Sex
http://ghahreei.eu.interia.pl
Ingenuity, she obtained every advantage for him should be
named, first of all, the congressional do you mean? I think
you told me,
Hi ,
we have made some changes to the driver mainly in the function igb_tso_adv and
some ugly patches to the stack .
If you like we can share the code and results of what we got so far.
one issue that is not clear is whether we need to re-edit the UDP length field
as it arrives to the driver.
Hi,
I see this stat being increased meaning the tx ring is getting full and i
want to avoid that. it might be that the cleanup of tx ring buffer is slow.
In e1000 there is TxIntDelay that you recomment to lower its value for
faster tx cleanup. IS there something similar for ixgbe?
Thanks,
Benzi
Flow control is disabled.
Can you explain please why *decreasing* (and not increasing) the tx ring
buffer will help avoiding tx_restart_queue?
Regarding InterruptThrottleRate, do you mean that setting it to higher value
may also prevent tx_restart_queue by faster tx ring cleanup?
On Mon, Apr 20,
On Monday 20 April 2009, Thadeu Lima de Souza Cascardo wrote:
After experimenting with kexec with the last merges after 2.6.29, I've
had some problems when probing e100. It would not read the eeprom. After
some bisects, I realized this has been like that since forever (at least
2.6.18). The
On Sun, 19 Apr 2009, Andrey Luzgin wrote:
We have repeating problems on several servers with different versions of
the driver e1000e with kernel 2.6.28.9 (this version because of tproxy
is necessary to us). All servers is Intel® Server Systems SR1560SF with
one additional NIC 82572EI Gigabit
On Mon, 20 Apr 2009, Benzi wrote:
Flow control is disabled.
okay good.
Can you explain please why *decreasing* (and not increasing) the tx ring
buffer will help avoiding tx_restart_queue?
the memory allocation and number of cachelines/pages being accessed goes
from 1 page (at 256
On Mon, 20 Apr 2009, Holger Eitzenberger wrote:
e1000e: write protect ICHx NVM to prevent malicious write/erase
no, doesn't apply to this hardware, as it is not ICH (integrated LOM) it
is a standalone 82571 with an actual discreet eeprom chip per port.
to include our modules
14 matches
Mail list logo
