search for: ethool

I recently noticed that after starting xend ethtool no longer work for my e1000 card. In my 2.X box which is a P4, ethtool is working after xend start. Same version of e1000 on both boxes. The unstable box is a Tyan 2462 SMP, FC4 dom0 The 2.X box is Dell P330 UP, Centos 4.1 domO Until xend start ethtool is fine, in both setups I am using the e1000 as eth0. Regards, Ted

...e, we'd resume > > the work for hiding lower netdev at that point. Think it would be the > > best to make everyone understand the big picture in advance before > > going too far. > > I think we should get the 3-netdev model integrated and add any additional > ndo_ops/ethool ops that we would like to support/migrate before looking into > hiding the lower netdevs. Once they are exposed, I don't think we'll be able to hide them - they will be a kernel ABI. Do you think everyone needs to hide the SRIOV device? Or that only some users need this? -- MST

...ork for hiding lower netdev at that point. Think it would be the > > > > best to make everyone understand the big picture in advance before > > > > going too far. > > > I think we should get the 3-netdev model integrated and add any additional > > > ndo_ops/ethool ops that we would like to support/migrate before looking into > > > hiding the lower netdevs. > > Once they are exposed, I don't think we'll be able to hide them - > > they will be a kernel ABI. > > > > Do you think everyone needs to hide the SRIOV device?...

On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote: > On 1/1/2015 9:41 PM, mechy2k2000 wrote: > > Hello I am thinking of buying this card to and wanted to know if this NIC > > is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit > > Ethernet Adapter QGEXPCI 501-6738-10. Can't find any info on how well the > > card plays with centos and also

...resume >>> the work for hiding lower netdev at that point. Think it would be the >>> best to make everyone understand the big picture in advance before >>> going too far. >> I think we should get the 3-netdev model integrated and add any additional >> ndo_ops/ethool ops that we would like to support/migrate before looking into >> hiding the lower netdevs. > Once they are exposed, I don't think we'll be able to hide them - > they will be a kernel ABI. > > Do you think everyone needs to hide the SRIOV device? > Or that only some user...

...esnt play nice with Linux. I also intend to use > the card with Proxmox VE which is debian based. > Why not instead buy an Intel Quad port NIC? Something you _know_ will be well supported. While I'm using a dual port PCI-X NIC and not a quad, I'm really happy with the compatibility (ethool can blink the LEDs) and have no complaints about performance. It is an Intel 82571EB using the e1000e kernel driver. lspci (for one interface of the dual) output below: ~]# lspci -s 08:00 -vv 08:00.0 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) Subsystem: I...

I ran this with a few folks offline and gathered some good feedbacks that I'd like to share thus revive the discussion. First of all, as illustrated in the reply below, cloud service providers require transparent live migration. Specifically, the main target of our case is to support SR-IOV live migration via kernel upgrade while keeping the userspace of old distros unmodified. If it's

...r hiding lower netdev at that point. Think it would be the >>>>> best to make everyone understand the big picture in advance before >>>>> going too far. >>>> I think we should get the 3-netdev model integrated and add any additional >>>> ndo_ops/ethool ops that we would like to support/migrate before looking into >>>> hiding the lower netdevs. >>> Once they are exposed, I don't think we'll be able to hide them - >>> they will be a kernel ABI. >>> >>> Do you think everyone needs to hide the S...

...ce all needed features get done, we'd resume > the work for hiding lower netdev at that point. Think it would be the > best to make everyone understand the big picture in advance before > going too far. I think we should get the 3-netdev model integrated and add any additional ndo_ops/ethool ops that we would like to support/migrate before looking into hiding the lower netdevs. > > Thanks, comments welcome. > > -Siwei > > > On Mon, Apr 9, 2018 at 11:48 PM, Siwei Liu <loseweigh at gmail.com> wrote: >> On Sun, Apr 8, 2018 at 9:32 AM, David Miller <da...

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. Changes from v5: - Align the implementation with the RFC spec update v4 - Switch the mode between single mode and multiqueue mode without reset - Remove the 256 limitation

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. Changes from v5: - Align the implementation with the RFC spec update v4 - Switch the mode between single mode and multiqueue mode without reset - Remove the 256 limitation

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. A protype implementation of qemu-kvm support could by found in git://github.com/jasowang/qemu-kvm-mq.git. To start a guest with two queues, you could specify the queues

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. A protype implementation of qemu-kvm support could by found in git://github.com/jasowang/qemu-kvm-mq.git. To start a guest with two queues, you could specify the queues

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. A protype implementation of qemu-kvm support could by found in git://github.com/jasowang/qemu-kvm-mq.git. To start a guest with two queues, you could specify the queues

Hi all: This series is an update version of multiqueue virtio-net driver based on Krishna Kumar's work to let virtio-net use multiple rx/tx queues to do the packets reception and transmission. Please review and comments. A protype implementation of qemu-kvm support could by found in git://github.com/jasowang/qemu-kvm-mq.git. To start a guest with two queues, you could specify the queues