From: Carsten Aulbert <carsten.aulbert@aei.mpg.de>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: netdev@vger.kernel.org, e1000-devel@lists.sourceforge.net
Subject: Re: Channel bonding with e1000
Date: Tue, 09 Sep 2008 08:21:08 +0200 [thread overview]
Message-ID: <48C615D4.30409@aei.mpg.de> (raw)
In-Reply-To: <alpine.WNT.1.10.0809081133290.7512@jbrandeb-MOBL1.amr.corp.intel.com>
Hi Jesse,
Brandeburg, Jesse wrote:
>> 05:02.0 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>> 05:02.1 Ethernet controller: Intel Corporation 82546GB Gigabit Ethernet
>> Controller (rev 03)
>
> This chip is connected over PCI-X and should be significantly slower
> and/or higher CPU utilization than the ESB2 based chip.
At first I couldn't believe it since I put in some of the cards myself
and those were PCIe x1 cards. But checking with lshw it looks you are
right (and the expert anyway):
*-pci:1
description: PCI bridge
product: 6311ESB/6321ESB PCI Express to PCI-X Bridge
vendor: Intel Corporation
physical id: 0.3
bus info: pci@01:00.3
version: 01
width: 32 bits
clock: 33MHz
capabilities: pci normal_decode bus_master cap_list
*-network:0 DISABLED
description: Ethernet interface
product: 82546GB Gigabit Ethernet Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@05:02.0
logical name: eth2
version: 03
serial: 00:1b:21:0d:c4:2c
capacity: 1GB/s
width: 64 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical
tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=e1000 driverversion=7.3.20-k2-NAPI firmware=N/A latency=52
link=no mingnt=255 multicast=yes port=twisted pair
resources: iomemory:d8080000-d809ffff
iomemory:d8000000-d803ffff ioport:3000-303f irq:28
*-network:1
description: Ethernet interface
product: 82546GB Gigabit Ethernet Controller
vendor: Intel Corporation
physical id: 2.1
bus info: pci@05:02.1
logical name: eth3
version: 03
serial: 00:1b:21:0d:c4:2d
size: 100MB/s
capacity: 1GB/s
width: 64 bits
clock: 66MHz
capabilities: bus_master cap_list ethernet physical
tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes
driver=e1000 driverversion=7.3.20-k2-NAPI duplex=full firmware=N/A
ip=172.28.11.4 latency=52 link=yes mingnt=255 multicast=yes port=twisted pai
r speed=100MB/s
resources: iomemory:d80a0000-d80bffff
iomemory:d8040000-d807ffff ioport:3040-307f irq:29
>
> It shouldn't matter, but I would take into consideration that the ESB2
> ports should be faster.
>
We'll start looking into this soon and try to get some tests underway.
>
> PS in the future questions like this could be cc:'d to
> e1000-devel@lists.sourceforge.net where all the Intel wired developers
> hang out (in addition to netdev)
Sorry, I should have remembered that one from ~6-9 months ago. Sorry,
I'll start with that mid-thread (and another sorry for that).
Cheers
Carsten
prev parent reply other threads:[~2008-09-09 6:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 8:36 Channel bonding with e1000 Carsten Aulbert
2008-09-05 14:37 ` Jay Vosburgh
2008-09-06 1:36 ` Bill Fink
2008-09-06 8:53 ` Carsten Aulbert
2008-09-08 18:37 ` Brandeburg, Jesse
2008-09-09 6:21 ` Carsten Aulbert [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48C615D4.30409@aei.mpg.de \
--to=carsten.aulbert@aei.mpg.de \
--cc=e1000-devel@lists.sourceforge.net \
--cc=jesse.brandeburg@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.