LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
* 1000xf bus problem
@ 2007-03-18 18:51 Greg.Chandler
  0 siblings, 0 replies; 9+ messages in thread
From: Greg.Chandler @ 2007-03-18 18:51 UTC (permalink / raw)
  To: e1000-devel; +Cc: linux-kernel


I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel
site shows this is a supported config for the card, but linux is pulling
this info:

ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit Ethernet
Controller (Fiber) (rev 02)
	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
      Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
      I/O ports at 7000 [size=32]
      [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
      Capabilities: [dc] Power Management version 2
      Capabilities: [e4] PCI-X non-bridge device
      Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-

My thoughput tests show it is definitely not running at the 100Mhz bus
rate is should be capable of.
Any ideas on how to make it work at full speed?

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 1000xf bus problem
  2007-03-19  5:20     ` Robert Hancock
@ 2007-03-19  5:31       ` Willy Tarreau
  0 siblings, 0 replies; 9+ messages in thread
From: Willy Tarreau @ 2007-03-19  5:31 UTC (permalink / raw)
  To: Robert Hancock; +Cc: Greg.Chandler, linux-kernel, e1000-devel

On Sun, Mar 18, 2007 at 11:20:09PM -0600, Robert Hancock wrote:
> Greg.Chandler@wellsfargo.com wrote:
> >lspci -v shows the message below, and I am moving files between systems,
> >{from RAMdisk to RAMdisk} on idle machines.
> >The transfer rate is concurrent with just under the max throughput
> >capable on a 64-bit/66Mhz PCI socket.
> 
> I think you miscalculate, that bus can transfer 532 MB/sec, Gigabit 
> Ethernet tops out at 125 MB/sec at absolute maximum and it's difficult 
> to achieve that in practice.

On TCP payload, you should achieve 118.66 * 10^6 bytes/s ~= 113 MB/s.
This is what you should observe with FTP or netcat for instance. On
local networks, it is perfectly attainable, I do this every day. If you
are far from this, check both sides link status with ethtool, and ensure
that you do not have wiring problems. It is usually very easy to fill the
wire with an e1000.

Also, it would be interesting to check the other side. What card does it
have, what bus, what driver ? And what software or tests are you using
to conclude that you're limited by the bus ?

Regards,
Willy


^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 1000xf bus problem
  2007-03-19  2:53   ` Greg.Chandler
@ 2007-03-19  5:20     ` Robert Hancock
  2007-03-19  5:31       ` Willy Tarreau
  0 siblings, 1 reply; 9+ messages in thread
From: Robert Hancock @ 2007-03-19  5:20 UTC (permalink / raw)
  To: Greg.Chandler; +Cc: linux-kernel, e1000-devel

Greg.Chandler@wellsfargo.com wrote:
> lspci -v shows the message below, and I am moving files between systems,
> {from RAMdisk to RAMdisk} on idle machines.
> The transfer rate is concurrent with just under the max throughput
> capable on a 64-bit/66Mhz PCI socket.

I think you miscalculate, that bus can transfer 532 MB/sec, Gigabit 
Ethernet tops out at 125 MB/sec at absolute maximum and it's difficult 
to achieve that in practice.

And what lspci reports is merely that the device supports 66MHz bus 
speed. That doesn't mean it doesn't support higher speeds and that 
doesn't mean that's what it's running at.

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: 1000xf bus problem
  2007-03-19  3:39       ` Kok, Auke
@ 2007-03-19  3:48         ` Greg.Chandler
  0 siblings, 0 replies; 9+ messages in thread
From: Greg.Chandler @ 2007-03-19  3:48 UTC (permalink / raw)
  To: auke-jan.h.kok; +Cc: hancockr, linux-kernel, e1000-devel


That would completely and uttly suck if it were the case.
So in theory, the card should be talking at full speed, but since the
bridge is 66 then it would be the bottleneck right?

There are 3 pci busses in the server I am working on, so I know there is
at least _a_ bridge there.....
 

-----Original Message-----
From: Kok, Auke [mailto:auke-jan.h.kok@intel.com] 
Sent: Sunday, March 18, 2007 10:40 PM
To: Chandler, Greg
Cc: auke-jan.h.kok@intel.com; hancockr@shaw.ca;
linux-kernel@vger.kernel.org; e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem

Greg.Chandler@wellsfargo.com wrote:
> If you mean dmesg it says this:
> e1000: 0000:0d:02.0: e1000_probe: (PCI-X:100MHz:64-bit)  {macaddress}
> 
> That's weird... dmesg shows one thing, lspci shows another, and my 
> data transfers seem to point to the lspci info...
> 
> Any idea which I should trust?


Both, the e1000 driver asks the card what it sees from it's side of the
connection, and lspci tells you what the cpu side of it is connected to.

Since stuff like pci bridges exist, both could very well be correct!

I highly suspect that that is exactly the case.


Auke



^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 1000xf bus problem
  2007-03-19  3:03     ` Greg.Chandler
@ 2007-03-19  3:39       ` Kok, Auke
  2007-03-19  3:48         ` Greg.Chandler
  0 siblings, 1 reply; 9+ messages in thread
From: Kok, Auke @ 2007-03-19  3:39 UTC (permalink / raw)
  To: Greg.Chandler; +Cc: auke-jan.h.kok, hancockr, linux-kernel, e1000-devel

Greg.Chandler@wellsfargo.com wrote:
> If you mean dmesg it says this:
> e1000: 0000:0d:02.0: e1000_probe: (PCI-X:100MHz:64-bit)  {macaddress}
> 
> That's weird... dmesg shows one thing, lspci shows another, and my data
> transfers seem to point to the lspci info...
> 
> Any idea which I should trust?


Both, the e1000 driver asks the card what it sees from it's side of the 
connection, and lspci tells you what the cpu side of it is connected to.

Since stuff like pci bridges exist, both could very well be correct!

I highly suspect that that is exactly the case.


Auke

^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: 1000xf bus problem
  2007-03-18 20:51   ` Kok, Auke
@ 2007-03-19  3:03     ` Greg.Chandler
  2007-03-19  3:39       ` Kok, Auke
  0 siblings, 1 reply; 9+ messages in thread
From: Greg.Chandler @ 2007-03-19  3:03 UTC (permalink / raw)
  To: auke-jan.h.kok, hancockr; +Cc: linux-kernel, e1000-devel


If you mean dmesg it says this:
e1000: 0000:0d:02.0: e1000_probe: (PCI-X:100MHz:64-bit)  {macaddress}

That's weird... dmesg shows one thing, lspci shows another, and my data
transfers seem to point to the lspci info...

Any idea which I should trust?


-----Original Message-----
From: Kok, Auke [mailto:auke-jan.h.kok@intel.com] 
Sent: Sunday, March 18, 2007 3:52 PM
To: Robert Hancock
Cc: Chandler, Greg; linux-kernel; e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem

Robert Hancock wrote:
> Greg.Chandler@wellsfargo.com wrote:
>> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel

>> site shows this is a supported config for the card, but linux is 
>> pulling this info:
>>
>> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit 
>> Ethernet Controller (Fiber) (rev 02)
>> 	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
>> 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
>> 	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
>>       Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
>>       I/O ports at 7000 [size=32]
>>       [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
>>       Capabilities: [dc] Power Management version 2
>>       Capabilities: [e4] PCI-X non-bridge device
>>       Capabilities: [f0] Message Signalled Interrupts: 64bit+ 
>> Queue=0/0
>> Enable-
>>
>> My thoughput tests show it is definitely not running at the 100Mhz 
>> bus rate is should be capable of.
> 
> How are you determining this?
> 
>  > Any ideas on how to make it work at full speed?

what is the dmesh output of e1000 ? it should show you what the card
itself detects (at least the newer drivers since 7.0.x all do). This may
provide some clues as to what the card has detected.

Auke



^ permalink raw reply	[flat|nested] 9+ messages in thread

* RE: 1000xf bus problem
  2007-03-18 19:41 ` Robert Hancock
  2007-03-18 20:51   ` Kok, Auke
@ 2007-03-19  2:53   ` Greg.Chandler
  2007-03-19  5:20     ` Robert Hancock
  1 sibling, 1 reply; 9+ messages in thread
From: Greg.Chandler @ 2007-03-19  2:53 UTC (permalink / raw)
  To: hancockr, linux-kernel; +Cc: e1000-devel


lspci -v shows the message below, and I am moving files between systems,
{from RAMdisk to RAMdisk} on idle machines.
The transfer rate is concurrent with just under the max throughput
capable on a 64-bit/66Mhz PCI socket.
 

-----Original Message-----
From: Robert Hancock [mailto:hancockr@shaw.ca] 
Sent: Sunday, March 18, 2007 2:41 PM
To: Chandler, Greg; linux-kernel
Cc: e1000-devel@lists.sourceforge.net
Subject: Re: 1000xf bus problem

Greg.Chandler@wellsfargo.com wrote:
> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel 
> site shows this is a supported config for the card, but linux is 
> pulling this info:
> 
> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit 
> Ethernet Controller (Fiber) (rev 02)
> 	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
> 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
> 	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
>       Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
>       I/O ports at 7000 [size=32]
>       [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
>       Capabilities: [dc] Power Management version 2
>       Capabilities: [e4] PCI-X non-bridge device
>       Capabilities: [f0] Message Signalled Interrupts: 64bit+ 
> Queue=0/0
> Enable-
> 
> My thoughput tests show it is definitely not running at the 100Mhz bus

> rate is should be capable of.

How are you determining this?

 > Any ideas on how to make it work at full speed?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca Home Page:
http://www.roberthancock.com/




^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 1000xf bus problem
  2007-03-18 19:41 ` Robert Hancock
@ 2007-03-18 20:51   ` Kok, Auke
  2007-03-19  3:03     ` Greg.Chandler
  2007-03-19  2:53   ` Greg.Chandler
  1 sibling, 1 reply; 9+ messages in thread
From: Kok, Auke @ 2007-03-18 20:51 UTC (permalink / raw)
  To: Robert Hancock; +Cc: Greg.Chandler, linux-kernel, e1000-devel

Robert Hancock wrote:
> Greg.Chandler@wellsfargo.com wrote:
>> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel
>> site shows this is a supported config for the card, but linux is pulling
>> this info:
>>
>> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit Ethernet
>> Controller (Fiber) (rev 02)
>> 	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
>> 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
>> 	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
>>       Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
>>       I/O ports at 7000 [size=32]
>>       [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
>>       Capabilities: [dc] Power Management version 2
>>       Capabilities: [e4] PCI-X non-bridge device
>>       Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
>> Enable-
>>
>> My thoughput tests show it is definitely not running at the 100Mhz bus
>> rate is should be capable of.
> 
> How are you determining this?
> 
>  > Any ideas on how to make it work at full speed?

what is the dmesh output of e1000 ? it should show you what the card itself 
detects (at least the newer drivers since 7.0.x all do). This may provide some 
clues as to what the card has detected.

Auke

^ permalink raw reply	[flat|nested] 9+ messages in thread

* Re: 1000xf bus problem
       [not found] <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
@ 2007-03-18 19:41 ` Robert Hancock
  2007-03-18 20:51   ` Kok, Auke
  2007-03-19  2:53   ` Greg.Chandler
  0 siblings, 2 replies; 9+ messages in thread
From: Robert Hancock @ 2007-03-18 19:41 UTC (permalink / raw)
  To: Greg.Chandler, linux-kernel; +Cc: e1000-devel

Greg.Chandler@wellsfargo.com wrote:
> I'm running a e1000xf adapter in a 64-bit/100Mhz PCI slot.  The intel
> site shows this is a supported config for the card, but linux is pulling
> this info:
> 
> ed:02.0 Ethernet controller: Intel Corporation 82544EI Gigabit Ethernet
> Controller (Fiber) (rev 02)
> 	Subsystem: Intel Corporation PRO/1000 XF Server Adapter
> 	Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 18
> 	Memory at f7fe0000 (64-bit, non-prefetchable) [size=128K]
>       Memory at f7fc0000 (64-bit, non-prefetchable) [size=128K]
>       I/O ports at 7000 [size=32]
>       [virtual] Expansion ROM at f10a0000 [disabled] [size=128K]
>       Capabilities: [dc] Power Management version 2
>       Capabilities: [e4] PCI-X non-bridge device
>       Capabilities: [f0] Message Signalled Interrupts: 64bit+ Queue=0/0
> Enable-
> 
> My thoughput tests show it is definitely not running at the 100Mhz bus
> rate is should be capable of.

How are you determining this?

 > Any ideas on how to make it work at full speed?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/


^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2007-03-19  5:32 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-03-18 18:51 1000xf bus problem Greg.Chandler
     [not found] <fa.wDPF1lWlqGQpxbyWee64Z3t4BVM@ifi.uio.no>
2007-03-18 19:41 ` Robert Hancock
2007-03-18 20:51   ` Kok, Auke
2007-03-19  3:03     ` Greg.Chandler
2007-03-19  3:39       ` Kok, Auke
2007-03-19  3:48         ` Greg.Chandler
2007-03-19  2:53   ` Greg.Chandler
2007-03-19  5:20     ` Robert Hancock
2007-03-19  5:31       ` Willy Tarreau

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).