search for: mlx4

tree: https://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git linux-next head: b5fe11663b48ca267829b34a65b4133e4e34c993 commit: 1f4098ea671b092af3806789d89e278e1f08e222 [4/11] mlx4: use new txqueue timeout argument config: sparc64-allmodconfig (attached as .config) compiler: sparc64-linux-gcc (GCC) 7.5.0 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross git checkout 1f...

Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c index aa348230bd39..2c2ff1f0ea6d 100644 --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c +++ b/drivers/...

Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/net/ethernet/mellanox/mlx4/en_netdev.c | 14 ++++---------- 1 file changed, 4 insertions(+), 10 deletions(-) diff --git a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c b/drivers/net/ethernet/mellanox/mlx4/en_netdev.c index aa348230bd39..2c2ff1f0ea6d 100644 --- a/drivers/net/ethernet/mellanox/mlx4/en_netdev.c +++ b/drivers/...

...eier <rolandd at cisco.com> Cc: Pavel Emelianov <xemul at openvz.org> Cc: Dan Williams <dcbw at redhat.com> Cc: libertas-dev at lists.infradead.org --- drivers/net/cxgb3/sge.c | 27 --------------------------- drivers/net/loopback.c | 2 -- drivers/net/mlx4/en_tx.c | 4 ---- drivers/net/niu.c | 3 +-- drivers/net/veth.c | 2 -- drivers/net/wireless/libertas/tx.c | 3 --- net/core/dev.c | 21 +++++---------------- 7 files changed, 6 insertions(+), 56 deletions(-) diff --git a...

...eier <rolandd at cisco.com> Cc: Pavel Emelianov <xemul at openvz.org> Cc: Dan Williams <dcbw at redhat.com> Cc: libertas-dev at lists.infradead.org --- drivers/net/cxgb3/sge.c | 27 --------------------------- drivers/net/loopback.c | 2 -- drivers/net/mlx4/en_tx.c | 4 ---- drivers/net/niu.c | 3 +-- drivers/net/veth.c | 2 -- drivers/net/wireless/libertas/tx.c | 3 --- net/core/dev.c | 21 +++++---------------- 7 files changed, 6 insertions(+), 56 deletions(-) diff --git a...

We have a new install of CentOS 6.7 with infiniband support installed. We can see the card in hardware and we can see the mlx4 drivers loaded in the kernel but cannot see the card as an ethernet interface, using ifconfig -a. Can you recommend an install procedure to see this as an ethernet interface? Thanks On 05/25/2016 07:32 AM, Fabian Arrotin wrote: > On 25/05/16 03:08, Pat Haley wrote: >> Hi All, >&gt...

...onfiguring_the_base_rdma_subsystemedit however we are getting conflicting information on whether the RDMA is correctly configured.??? Some of what we have done and some of the data are below. Can you suggest what other tests and what other data we should get to debug this problem? /etc/rdma/mlx4.conf to set the port types properly for RoCE/IBoE usage. Edit /etc/modprobe.d/mlx4.conf to instruct the driver on which packet priority is configured for the ?no-drop? service on the Ethernet switches the cards are plugged into. vim /etc/rdma/mlx4.conf You can find the right pci device to use...

...; To make it work for OOO backends I think we need something like this >> (hardware NIC drivers are usually have something like this). > Which hardware NIC drivers have this? It's quite common I think, e.g driver track e.g dma addr and page frag somewhere. e.g the ring->rx_info in mlx4 driver. Thanks > >> Not for the patch, but it looks like having a OUT_OF_ORDER feature bit is >> much more simpler to be started with. > +1 > > Best regards, > Tiwei Bie

...; To make it work for OOO backends I think we need something like this >> (hardware NIC drivers are usually have something like this). > Which hardware NIC drivers have this? It's quite common I think, e.g driver track e.g dma addr and page frag somewhere. e.g the ring->rx_info in mlx4 driver. Thanks > >> Not for the patch, but it looks like having a OUT_OF_ORDER feature bit is >> much more simpler to be started with. > +1 > > Best regards, > Tiwei Bie

Hi All, We looking for suggestions on dealing with mellanox drivers in CentOS 6.7 We tried installing mellanox drivers (MLNX_OFED_LINUX-3.2-2.0.0.0-rhel6.7-x86_64) on a Quanta Cirrascale server running Centos 6.7 - 2.6.32-573.22.1.el6.x86_64. When we rebooted the machine after installing the drivers, it went into a kernel panic for every installed kernel except for Centos 6.7

...d of tx/rx processing, busy polling for new tx added descriptor and rx receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test A were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected mlx4 - Guest with 1 vcpus and 1 queue Results: - Obvious improvements (%5 - 20%) for latency (TCP_RR). - Get a better or minor regression on most of the TX tests, but see some regression on 4096 size. - Except for 8 sessions of 4096 size RX, have a better or same performance. - CPU utilization were...

...d of tx/rx processing, busy polling for new tx added descriptor and rx receive socket for a while. The maximum number of time (in us) could be spent on busy polling was specified ioctl. Test A were done through: - 50 us as busy loop timeout - Netperf 2.6 - Two machines with back to back connected mlx4 - Guest with 1 vcpus and 1 queue Results: - Obvious improvements (%5 - 20%) for latency (TCP_RR). - Get a better or minor regression on most of the TX tests, but see some regression on 4096 size. - Except for 8 sessions of 4096 size RX, have a better or same performance. - CPU utilization were...

...ds I think we need something like this >>>> (hardware NIC drivers are usually have something like this). >>> Which hardware NIC drivers have this? >> It's quite common I think, e.g driver track e.g dma addr and page frag >> somewhere. e.g the ring->rx_info in mlx4 driver. > It seems that I had a misunderstanding on your > previous comments. I know it's quite common for > drivers to track e.g. DMA addrs somewhere (and > I think one reason behind this is that they want > to reuse the bits of addr field). Yes, we may want this for virtio-net...

...ds I think we need something like this >>>> (hardware NIC drivers are usually have something like this). >>> Which hardware NIC drivers have this? >> It's quite common I think, e.g driver track e.g dma addr and page frag >> somewhere. e.g the ring->rx_info in mlx4 driver. > It seems that I had a misunderstanding on your > previous comments. I know it's quite common for > drivers to track e.g. DMA addrs somewhere (and > I think one reason behind this is that they want > to reuse the bits of addr field). Yes, we may want this for virtio-net...

...that exists to that SKB. > > And exactly for the case you are trying to "fix" here, you do not. If > the SKB is cloned, or has an elevated users count, someone else can be > looking at it exactly at the same time you are messing with the data > pointers. > > I bet mlx4 has this bug too. > > You must fix this properly, by keeping track of an offset or similar > internally to your driver, rather than changing the SKB data pointers. What virtio does is this: can_push = vi->any_header_sg && !((unsigned long)skb->data...

...that exists to that SKB. > > And exactly for the case you are trying to "fix" here, you do not. If > the SKB is cloned, or has an elevated users count, someone else can be > looking at it exactly at the same time you are messing with the data > pointers. > > I bet mlx4 has this bug too. > > You must fix this properly, by keeping track of an offset or similar > internally to your driver, rather than changing the SKB data pointers. What virtio does is this: can_push = vi->any_header_sg && !((unsigned long)skb->data...

...important, vhost could not benefit from commit commit 9e641bdcfa4e ("net-tun: restructure tun_do_read for better sleep/wakeup efficiency") even if we've stopped rx polling during handle_rx() since tx poll were still left in the waitqueue. Pktgen from a remote host to VM over mlx4 shows 5.5% improvements on rx PPS. (from 1.27Mpps to 1.34Mpps) Cc: Wei Xu <wexu at redhat.com> Cc: Matthew Rosato <mjrosato at linux.vnet.ibm.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 dele...

...important, vhost could not benefit from commit commit 9e641bdcfa4e ("net-tun: restructure tun_do_read for better sleep/wakeup efficiency") even if we've stopped rx polling during handle_rx() since tx poll were still left in the waitqueue. Pktgen from a remote host to VM over mlx4 shows 5.5% improvements on rx PPS. (from 1.27Mpps to 1.34Mpps) Cc: Wei Xu <wexu at redhat.com> Cc: Matthew Rosato <mjrosato at linux.vnet.ibm.com> Signed-off-by: Jason Wang <jasowang at redhat.com> --- drivers/vhost/net.c | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 dele...

On Tue, Jan 24, 2017 at 7:48 PM, John Fastabend <john.fastabend at gmail.com> wrote: > > It is a concern on my side. I want XDP and Linux stack to work > reasonably well together. btw the micro benchmarks showed that page per packet approach that xdp took in mlx4 should be 10% slower vs normal operation for tcp/ip stack. We thought that for our LB use case it will be an acceptable slowdown, but turned out that overall we got a performance boost, since xdp model simplified user space and got data path faster, so we magically got extra free cpu that is used f...

On Tue, Jan 24, 2017 at 7:48 PM, John Fastabend <john.fastabend at gmail.com> wrote: > > It is a concern on my side. I want XDP and Linux stack to work > reasonably well together. btw the micro benchmarks showed that page per packet approach that xdp took in mlx4 should be 10% slower vs normal operation for tcp/ip stack. We thought that for our LB use case it will be an acceptable slowdown, but turned out that overall we got a performance boost, since xdp model simplified user space and got data path faster, so we magically got extra free cpu that is used f...