search for: rx_info

Displaying 11 results from an estimated 11 matches for "rx_info".

Did you mean: r_info
2018 May 17
2
[RFC v4 3/5] virtio_ring: add packed ring support
...ng? >> 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
2018 May 17
2
[RFC v4 3/5] virtio_ring: add packed ring support
...ng? >> 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
2018 May 18
2
[RFC v4 3/5] virtio_ring: add packed ring support
...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. > 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 vi...
2018 May 18
2
[RFC v4 3/5] virtio_ring: add packed ring support
...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. > 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 vi...
2018 May 18
0
[RFC v4 3/5] virtio_ring: add packed ring support
...ork 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. 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). But tracking addrs somewhere doesn't means suppor...
2018 May 19
2
[RFC v4 3/5] virtio_ring: add packed ring support
...mething 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 ad...
2018 May 19
2
[RFC v4 3/5] virtio_ring: add packed ring support
...mething 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 ad...
2018 May 18
0
[RFC v4 3/5] virtio_ring: add packed ring support
...ed 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). >...
2018 May 19
0
[RFC v4 3/5] virtio_ring: add packed ring support
...t; > > > (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 > &gt...
2018 May 16
2
[RFC v4 3/5] virtio_ring: add packed ring support
On 2018?05?16? 21:45, Tiwei Bie wrote: > On Wed, May 16, 2018 at 08:51:43PM +0800, Jason Wang wrote: >> On 2018?05?16? 20:39, Tiwei Bie wrote: >>> On Wed, May 16, 2018 at 07:50:16PM +0800, Jason Wang wrote: >>>> On 2018?05?16? 16:37, Tiwei Bie wrote: >>> [...] >>>>> struct vring_virtqueue { >>>>> @@ -116,6 +117,9 @@ struct
2018 May 16
2
[RFC v4 3/5] virtio_ring: add packed ring support
On 2018?05?16? 21:45, Tiwei Bie wrote: > On Wed, May 16, 2018 at 08:51:43PM +0800, Jason Wang wrote: >> On 2018?05?16? 20:39, Tiwei Bie wrote: >>> On Wed, May 16, 2018 at 07:50:16PM +0800, Jason Wang wrote: >>>> On 2018?05?16? 16:37, Tiwei Bie wrote: >>> [...] >>>>> struct vring_virtqueue { >>>>> @@ -116,6 +117,9 @@ struct