Project Home
Project Home
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - using multiple Intel Pro 1000 network cards: (12 Items)
   
using multiple Intel Pro 1000 network cards  
Hi Robert,

We have a customer who is trying to run three network cards simultaneously.
Has anyone tried to do this? Is there anything that we need to be careful
with in trying to set this up?

I have included the complete email from our distributor, who is helping our
customer with this issue.

Thanks!!
- Ed
 

-----Original Message-----
From: Kjell Ragnhildrød [mailto:kjell@arxi.no] 
Sent: March 27, 2008 7:49 AM
To: Ed Lee; Larry Atkinson
Cc: Nancy Campbell; ARX Support
Subject: Optonova - Intel Pro 1000 driver support.

Ed/Larry,

How should we proceed on the issue below?

They are evaluating QNX and have some performance challenges with the
existing TCP/IP stack with Gigabit camera and other problems with the new
TCP/IP stack in beta.

They have a small fanless computer with two onboard network cards Intel Pro
1000 PL and one extra PCI express Intel Pro 1000 PT. Our goal is to connect
two GigaBit cameras to this computer.

When they start the network driver with: io-net -di82544 -ptcpip it will
(according to ifconfig) detect the two onbard cards.

They are now able to connect to a camera but the CPU load is very high
(around 50%) which means that when they connect the second camera and add
the image processing the load will probably be too high.

They have also downloaded the io-pkt package which claims to be both much
more efficient and also can handle jumboframes. When they now start the
driver with "io-pkt-v4 -di82544 -ptcpip" it detects all three network cards
but only the extra card
will work. Ifconfig is not able to detect the mac-address of the two onboard
cards (it reports ff:ff:ff:ff:ff:ff:ff for those) which we guess is related
to the problem. They are able to "ping" the camera though, even when it is
connected to
the cards with ff:ff:ff:ff:ff:ff mac address, but no other communication
works

Details:

PCI version    = 3.00

Class          = Display (VGA)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27a2h,  Mobile 945GM/GMS/940GML Express Integrated Graphics
Controller
PCI index      = 0h
PCI Mem Address = fdf00000h enabled
PCI IO Address  = ff00h enabled
PCI Mem Address = b0000000h enabled
PCI Mem Address = fdf80000h enabled
PCI Int Pin    = INT A
Interrupt line = 15
CPU Interrupt  = fh

Class          = Multimedia (Audio)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27deh,  82801G (ICH7 Family) AC'97 Audio Controller
PCI index      = 0h
PCI IO Address  = f000h enabled
PCI IO Address  = fa00h enabled
PCI Mem Address = fdffe000h enabled
PCI Mem Address = fdffd000h enabled
PCI Int Pin    = INT A
Interrupt line = 5
CPU Interrupt  = 5h

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27dfh,  82801G (ICH7 Family) IDE Controller
PCI index      = 0h
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = f800h enabled
PCI Int Pin    = INT A
Interrupt line = no connection

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27c4h,  82801GBM/GHM (ICH7 Family) Serial ATA Storage
Controller IDE
PCI index      = 0h
PCI IO Address  = f700h enabled
PCI IO Address  = f600h enabled
PCI IO Address  = f500h enabled
PCI IO Address  = f400h enabled
PCI IO Address  = f300h enabled
PCI Mem Address = fdffc000h enabled
PCI Int Pin    = INT B
Interrupt line = 15
CPU Interrupt  = fh

Class          = Network (Ethernet)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 10b9h, Unknown Unknown
PCI index      = 0h
PCI Mem Address = fd8e0000h enabled
PCI Mem Address = fd8c0000h enabled
PCI IO Address  = bf00h enabled
PCI Expansion ROM = 0h disabled
PCI Int Pin    = INT A
Interrupt line = 15
CPU Interrupt  = fh

Class          = Network (Ethernet)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 109ah,  82573L...
View Full Message
RE: using multiple Intel Pro 1000 network cards  
Looking at your pci output, I see
You have two different types of i82544
cards (did 0x10b9 and 0x109a).  I 
wonder if the driver is not seeing 
all of them (esp the 10b9?)

A newer driver might also be an idea ...
Because of all the new and different 
Chipsets supported by this driver (over 
60 hardware variants, last time I checked) 
it's getting updated frequently.

--
aboyd

-----Original Message-----
From: Ed Lee 
Sent: Thursday, March 27, 2008 9:14 AM
To: general-networking
Subject: using multiple Intel Pro 1000 network cards

Hi Robert,

We have a customer who is trying to run three network cards simultaneously.
Has anyone tried to do this? Is there anything that we need to be careful
with in trying to set this up?

I have included the complete email from our distributor, who is helping our
customer with this issue.

Thanks!!
- Ed
 

-----Original Message-----
From: Kjell Ragnhildrød [mailto:kjell@arxi.no] 
Sent: March 27, 2008 7:49 AM
To: Ed Lee; Larry Atkinson
Cc: Nancy Campbell; ARX Support
Subject: Optonova - Intel Pro 1000 driver support.

Ed/Larry,

How should we proceed on the issue below?

They are evaluating QNX and have some performance challenges with the
existing TCP/IP stack with Gigabit camera and other problems with the new
TCP/IP stack in beta.

They have a small fanless computer with two onboard network cards Intel Pro
1000 PL and one extra PCI express Intel Pro 1000 PT. Our goal is to connect
two GigaBit cameras to this computer.

When they start the network driver with: io-net -di82544 -ptcpip it will
(according to ifconfig) detect the two onbard cards.

They are now able to connect to a camera but the CPU load is very high
(around 50%) which means that when they connect the second camera and add
the image processing the load will probably be too high.

They have also downloaded the io-pkt package which claims to be both much
more efficient and also can handle jumboframes. When they now start the
driver with "io-pkt-v4 -di82544 -ptcpip" it detects all three network cards
but only the extra card
will work. Ifconfig is not able to detect the mac-address of the two onboard
cards (it reports ff:ff:ff:ff:ff:ff:ff for those) which we guess is related
to the problem. They are able to "ping" the camera though, even when it is
connected to
the cards with ff:ff:ff:ff:ff:ff mac address, but no other communication
works

Details:

PCI version    = 3.00

Class          = Display (VGA)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27a2h,  Mobile 945GM/GMS/940GML Express Integrated Graphics
Controller
PCI index      = 0h
PCI Mem Address = fdf00000h enabled
PCI IO Address  = ff00h enabled
PCI Mem Address = b0000000h enabled
PCI Mem Address = fdf80000h enabled
PCI Int Pin    = INT A
Interrupt line = 15
CPU Interrupt  = fh

Class          = Multimedia (Audio)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27deh,  82801G (ICH7 Family) AC'97 Audio Controller
PCI index      = 0h
PCI IO Address  = f000h enabled
PCI IO Address  = fa00h enabled
PCI Mem Address = fdffe000h enabled
PCI Mem Address = fdffd000h enabled
PCI Int Pin    = INT A
Interrupt line = 5
CPU Interrupt  = 5h

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27dfh,  82801G (ICH7 Family) IDE Controller
PCI index      = 0h
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = f800h enabled
PCI Int Pin    = INT A
Interrupt line = no connection

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27c4h,  82801GBM/GHM (ICH7 Family) Serial ATA Storage
Controller IDE
PCI index      = 0h
PCI IO Address  = f700h enabled
PCI IO Address  = f600h enabled
PCI IO Address  = f500h enabled
PCI IO Address  = f400h enabled
PCI IO Address  = f300h enabled
PCI Mem...
View Full Message
Re: RE: using multiple Intel Pro 1000 network cards  
Andrew, do you mean that there is already a newer driver that is or can be made available for testing?
Re: RE: using multiple Intel Pro 1000 network cards  
RE: using multiple Intel Pro 1000 network cards  
Hi Ed:
	We've got a bit of a driver dilemma here.  The GA io-net driver
likely isn't detecting one of the cards and the io-pkt driver needs some
updates to support reading from the EEPROMs of some newer cards (which is
why the MAC addresses are out of whack).  So what I would propose is this:

In this forum post, 
http://community.qnx.com/sf/discussion/do/listPosts/projects.bsp/discussion.
bsp.topc2188?pageSize=-1#post5716


Hugh attached an "experimental" build of the i82544 driver for io-net.  (See
the second posting).  I'd give this one a shot and see if that clears up the
io-net problem.

For io-pkt, I'm in the process of adding the NetBSD wm build directory to
the build so that you can try it out.  This driver isn't going to be a
supported driver, but it will let you at least kick the tires with the newer
cards until we get to updating our native driver.  That should be in some
time today or Monday.

	Robert.


-----Original Message-----
From: Kjell Ragnhildrød [mailto:kjell@arxi.no] 
Sent: March 27, 2008 7:49 AM
To: Ed Lee; Larry Atkinson
Cc: Nancy Campbell; ARX Support
Subject: Optonova - Intel Pro 1000 driver support.

Ed/Larry,

How should we proceed on the issue below?

They are evaluating QNX and have some performance challenges with the
existing TCP/IP stack with Gigabit camera and other problems with the new
TCP/IP stack in beta.

They have a small fanless computer with two onboard network cards Intel Pro
1000 PL and one extra PCI express Intel Pro 1000 PT. Our goal is to connect
two GigaBit cameras to this computer.

When they start the network driver with: io-net -di82544 -ptcpip it will
(according to ifconfig) detect the two onbard cards.

They are now able to connect to a camera but the CPU load is very high
(around 50%) which means that when they connect the second camera and add
the image processing the load will probably be too high.

They have also downloaded the io-pkt package which claims to be both much
more efficient and also can handle jumboframes. When they now start the
driver with "io-pkt-v4 -di82544 -ptcpip" it detects all three network cards
but only the extra card
will work. Ifconfig is not able to detect the mac-address of the two onboard
cards (it reports ff:ff:ff:ff:ff:ff:ff for those) which we guess is related
to the problem. They are able to "ping" the camera though, even when it is
connected to
the cards with ff:ff:ff:ff:ff:ff mac address, but no other communication
works

Details:

PCI version    = 3.00

Class          = Display (VGA)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27a2h,  Mobile 945GM/GMS/940GML Express Integrated Graphics
Controller
PCI index      = 0h
PCI Mem Address = fdf00000h enabled
PCI IO Address  = ff00h enabled
PCI Mem Address = b0000000h enabled
PCI Mem Address = fdf80000h enabled
PCI Int Pin    = INT A
Interrupt line = 15
CPU Interrupt  = fh

Class          = Multimedia (Audio)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27deh,  82801G (ICH7 Family) AC'97 Audio Controller
PCI index      = 0h
PCI IO Address  = f000h enabled
PCI IO Address  = fa00h enabled
PCI Mem Address = fdffe000h enabled
PCI Mem Address = fdffd000h enabled
PCI Int Pin    = INT A
Interrupt line = 5
CPU Interrupt  = 5h

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27dfh,  82801G (ICH7 Family) IDE Controller
PCI index      = 0h
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = 0h enabled
PCI IO Address  = f800h enabled
PCI Int Pin    = INT A
Interrupt line = no connection

Class          = Mass Storage (IDE)
Vendor ID      = 8086h, Intel Corporation
Device ID      = 27c4h,  82801GBM/GHM (ICH7 Family) Serial ATA Storage
Controller IDE
PCI index      = 0h
PCI IO Address  = f700h enabled
PCI IO Address  = f600h enabled
PCI IO Address  = f500h enabled
PCI IO...
View Full Message
Re: RE: using multiple Intel Pro 1000 network cards  
Hello guys,
we are the customer who are evaluating QNX with the described problem. I made an update and installed yesterdays version
 of io-pkt, and started it with

io-pkt-v4 -di82544 -ptcpip

However, I still only get ff:ff:ff:ff:ff:ff:ff for the internal network cards. Was there any fix made to solve the 
problem with reading from the EEPROM or is it still on the todo list? In the meantime, we can use io-net, which now 
detects all three network cards with the experimental driver.

Best regards,

Roland
RE: RE: using multiple Intel Pro 1000 network cards  
> io-pkt-v4 -di82544 -ptcpip
>
> However, I still only get ff:ff:ff:ff:ff:ff:ff 

Two thoughts:

1) Rob has fixed the eeprom code in the io-pkt
i82544 driver - not sure if he's checked it in
yet.  I think me and Sean were supposed to code
review it, and I dunno about Sean, but I haven't
yet - sorry!  :-(

2) you can use the io-net driver with io-pkt - 
just specify the full path to the io-net driver,
and io-pkt will automatically start the shim for
you.  There are actually 3 different drivers for
each of the i82544 and speedo for io-pkt.

--
aboyd
Re: RE: using multiple Intel Pro 1000 network cards  
On Wed, Apr 23, 2008 at 08:34:16AM -0400, Andrew Boyd wrote:
> 
> > io-pkt-v4 -di82544 -ptcpip
> >
> > However, I still only get ff:ff:ff:ff:ff:ff:ff 
> 
> Two thoughts:
> 
> 1) Rob has fixed the eeprom code in the io-pkt
> i82544 driver - not sure if he's checked it in
> yet.  I think me and Sean were supposed to code
> review it, and I dunno about Sean, but I haven't
> yet - sorry!  :-(

Code review is in progress.  It should hopefully be in soon.

-seanb
RE: RE: using multiple Intel Pro 1000 network cards  
How about giving this x86 version try.  It's "highly experimental" at this
point.

Just as a side note, you should try playing with the irq_thresh option to
the driver.  It will GREATLY reduce your CPU usage.  The optimal value will
depend upon how fast your CPU is.  I use a value of 8000 on a 2.2GHz x86.

On another note, you can also try the NetBSD wm driver which has the
advantage of including Transmit Segmentation Offload which can give you
markedly reduced CPU utilization for transmission of large amounts of data.

   Robert.

-----Original Message-----
From: Roland Waltersson [mailto:rolandva@kth.se] 
Sent: Wednesday, April 23, 2008 4:51 AM
To: general-networking
Subject: Re: RE: using multiple Intel Pro 1000 network cards

Hello guys,
we are the customer who are evaluating QNX with the described problem. I
made an update and installed yesterdays version of io-pkt, and started it
with

io-pkt-v4 -di82544 -ptcpip

However, I still only get ff:ff:ff:ff:ff:ff:ff for the internal network
cards. Was there any fix made to solve the problem with reading from the
EEPROM or is it still on the todo list? In the meantime, we can use io-net,
which now detects all three network cards with the experimental driver.

Best regards,

Roland

_______________________________________________
General
http://community.qnx.com/sf/go/post7195

Attachment: Text devnp-i82544.so 49.17 KB
Re: RE: RE: using multiple Intel Pro 1000 network cards  
Thanks again,
yes both the older experimental and this one worked fine with io-pkt. I will see how io-thresh affects the CPU load. Do 
you have any planned official release of the driver and io-pkt soon (except "2008" that is stated in the project roadmap
 :) )?

/ Roland
Re: RE: RE: using multiple Intel Pro 1000 network cards  
Please check info in private mail regarding release.
RE: RE: RE: using multiple Intel Pro 1000 network cards  
Hi Roland:
	That's good to know!  Now all I need to do is get the code finalized
and checked in.  You'll find that the irq_thresh (which is the total number
of interrupts per second that the card will produce) can make quite a
difference to CPU usage.  You'll find that, at some point, there's a
trade-off between raw throughput and CPU, so you adjust the number up until
you reach that point and that's where you leave it.  This mainly affects
receive performance although there will also be a smaller affect on transmit
for TCP (since ACK reception determines what happens with the TCP window).

  In terms of release date, we've been re-aligning the release to match up
with a major release of our whole product in the fall (io-pkt is
incorporated in this release as opposed to being a standlone install).
We're still trying to dot i's and cross t's on that one but should have more
information shortly.

	Robert.

-----Original Message-----
From: Roland Waltersson [mailto:rolandva@kth.se] 
Sent: Thursday, April 24, 2008 4:56 AM
To: general-networking
Subject: Re: RE: RE: using multiple Intel Pro 1000 network cards

Thanks again,
yes both the older experimental and this one worked fine with io-pkt. I will
see how io-thresh affects the CPU load. Do you have any planned official
release of the driver and io-pkt soon (except "2008" that is stated in the
project roadmap :) )?

/ Roland

_______________________________________________
General
http://community.qnx.com/sf/go/post7231