search for: id_talbe

Displaying 20 results from an estimated 31 matches for "id_talbe".

Did you mean: id_table
2019 Nov 06
2
[PATCH V8 0/6] mdev based hardware virtio offloading support
...n their own virtio datapath >> offloading product. >> >> Consider mdev framework only support VFIO device and driver right now, >> this series also extend it to support other types. This is done >> through introducing class id to the device and pairing it with >> id_talbe claimed by the driver. On top, this seris also decouple >> device specific parents ops out of the common ones. >> >> Pktgen test was done with virito-net + mvnet loop back device. >> >> Please review. >> >> [1] https://lkml.org/lkml/2019/10/31/440 >>...
2019 Nov 06
2
[PATCH V8 0/6] mdev based hardware virtio offloading support
...n their own virtio datapath >> offloading product. >> >> Consider mdev framework only support VFIO device and driver right now, >> this series also extend it to support other types. This is done >> through introducing class id to the device and pairing it with >> id_talbe claimed by the driver. On top, this seris also decouple >> device specific parents ops out of the common ones. >> >> Pktgen test was done with virito-net + mvnet loop back device. >> >> Please review. >> >> [1] https://lkml.org/lkml/2019/10/31/440 >>...
2019 Oct 15
2
[PATCH V3 0/7] mdev based hardware virtio offloading support
...as a reference implementation for real hardware driver. >> >> Consider mdev framework only support VFIO device and driver right now, >> this series also extend it to support other types. This is done >> through introducing class id to the device and pairing it with >> id_talbe claimed by the driver. On top, this seris also decouple >> device specific parents ops out of the common ones. > I was curious so I took a quick look and posted comments. > > I guess this driver runs inside the guest since it registers virtio > devices? It could run in either gu...
2019 Oct 15
2
[PATCH V3 0/7] mdev based hardware virtio offloading support
...as a reference implementation for real hardware driver. >> >> Consider mdev framework only support VFIO device and driver right now, >> this series also extend it to support other types. This is done >> through introducing class id to the device and pairing it with >> id_talbe claimed by the driver. On top, this seris also decouple >> device specific parents ops out of the common ones. > I was curious so I took a quick look and posted comments. > > I guess this driver runs inside the guest since it registers virtio > devices? It could run in either gu...
2019 Nov 06
2
[PATCH V8 0/6] mdev based hardware virtio offloading support
...oduct. > > >> > > >> Consider mdev framework only support VFIO device and driver right now, > > >> this series also extend it to support other types. This is done > > >> through introducing class id to the device and pairing it with > > >> id_talbe claimed by the driver. On top, this seris also decouple > > >> device specific parents ops out of the common ones. > > >> > > >> Pktgen test was done with virito-net + mvnet loop back device. > > >> > > >> Please review. > > >>...
2019 Nov 06
2
[PATCH V8 0/6] mdev based hardware virtio offloading support
...oduct. > > >> > > >> Consider mdev framework only support VFIO device and driver right now, > > >> this series also extend it to support other types. This is done > > >> through introducing class id to the device and pairing it with > > >> id_talbe claimed by the driver. On top, this seris also decouple > > >> device specific parents ops out of the common ones. > > >> > > >> Pktgen test was done with virito-net + mvnet loop back device. > > >> > > >> Please review. > > >>...
2019 Oct 17
1
[PATCH V3 0/7] mdev based hardware virtio offloading support
...hardware driver. >>>> >>>> Consider mdev framework only support VFIO device and driver right now, >>>> this series also extend it to support other types. This is done >>>> through introducing class id to the device and pairing it with >>>> id_talbe claimed by the driver. On top, this seris also decouple >>>> device specific parents ops out of the common ones. >>> I was curious so I took a quick look and posted comments. >>> >>> I guess this driver runs inside the guest since it registers virtio >>&...
2019 Oct 14
0
[PATCH V3 0/7] mdev based hardware virtio offloading support
...could be > used as a reference implementation for real hardware driver. > > Consider mdev framework only support VFIO device and driver right now, > this series also extend it to support other types. This is done > through introducing class id to the device and pairing it with > id_talbe claimed by the driver. On top, this seris also decouple > device specific parents ops out of the common ones. I was curious so I took a quick look and posted comments. I guess this driver runs inside the guest since it registers virtio devices? If this is used with physical PCI devices that s...
2019 Nov 05
0
[PATCH V8 0/6] mdev based hardware virtio offloading support
...ors who is interested in their own virtio datapath > offloading product. > > Consider mdev framework only support VFIO device and driver right now, > this series also extend it to support other types. This is done > through introducing class id to the device and pairing it with > id_talbe claimed by the driver. On top, this seris also decouple > device specific parents ops out of the common ones. > > Pktgen test was done with virito-net + mvnet loop back device. > > Please review. > > [1] https://lkml.org/lkml/2019/10/31/440 > [2] https://lkml.org/lkml/201...
2019 Nov 06
0
[PATCH V8 0/6] mdev based hardware virtio offloading support
...t; >> offloading product. > >> > >> Consider mdev framework only support VFIO device and driver right now, > >> this series also extend it to support other types. This is done > >> through introducing class id to the device and pairing it with > >> id_talbe claimed by the driver. On top, this seris also decouple > >> device specific parents ops out of the common ones. > >> > >> Pktgen test was done with virito-net + mvnet loop back device. > >> > >> Please review. > >> > >> [1] https://lkm...
2019 Oct 15
0
[PATCH V3 0/7] mdev based hardware virtio offloading support
...for real hardware driver. > > > > > > Consider mdev framework only support VFIO device and driver right now, > > > this series also extend it to support other types. This is done > > > through introducing class id to the device and pairing it with > > > id_talbe claimed by the driver. On top, this seris also decouple > > > device specific parents ops out of the common ones. > > I was curious so I took a quick look and posted comments. > > > > I guess this driver runs inside the guest since it registers virtio > > devices?...
2019 Nov 06
0
[PATCH V8 0/6] mdev based hardware virtio offloading support
...;> > > > >> Consider mdev framework only support VFIO device and driver right now, > > > >> this series also extend it to support other types. This is done > > > >> through introducing class id to the device and pairing it with > > > >> id_talbe claimed by the driver. On top, this seris also decouple > > > >> device specific parents ops out of the common ones. > > > >> > > > >> Pktgen test was done with virito-net + mvnet loop back device. > > > >> > > > >> Please r...
2019 Sep 25
0
[PATCH V2 0/8] mdev based hardware virtio offloading support
...could be > used as a reference implementation for real hardware driver. > > Consider mdev framework only support VFIO device and driver right now, > this series also extend it to support other types. This is done > through introducing class id to the device and pairing it with > id_talbe claimed by the driver. On top, this seris also decouple id_table claimed ... this series ... > device specific parents ops out of the common ones. > > Pktgen test was done with virito-net + mvnet loop back device. > > Please review. > > [1] https://lkml.org/lkml/2019/9/16/...
2019 Sep 20
8
[RFC PATCH V2 0/6] mdev based hardware virtio offloading support
...op of vringh + workqueue. This could be used as a reference implementation for real hardware driver. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific parents ops out of the common ones. Pktgen test was done with virito-net + mvnet loop back device. Please review. Changes from V1: - rename device id to class id - add docs for class id and device specific ops (device_ops)...
2019 Nov 05
15
[PATCH V8 0/6] mdev based hardware virtio offloading support
...h is a good reference for vendors who is interested in their own virtio datapath offloading product. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific parents ops out of the common ones. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/10/31/440 [2] https://lkml.org/lkml/2019/10/15/1226 Changes from V7: - drop {s...
2019 Nov 05
15
[PATCH V8 0/6] mdev based hardware virtio offloading support
...h is a good reference for vendors who is interested in their own virtio datapath offloading product. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific parents ops out of the common ones. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/10/31/440 [2] https://lkml.org/lkml/2019/10/15/1226 Changes from V7: - drop {s...
2019 Oct 11
17
[PATCH V3 0/7] mdev based hardware virtio offloading support
...op of vringh + workqueue. This could be used as a reference implementation for real hardware driver. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific parents ops out of the common ones. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/9/26/15 Changes from V2: - fail when class_id is not specified - drop the vri...
2019 Oct 11
17
[PATCH V3 0/7] mdev based hardware virtio offloading support
...op of vringh + workqueue. This could be used as a reference implementation for real hardware driver. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific parents ops out of the common ones. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/9/26/15 Changes from V2: - fail when class_id is not specified - drop the vri...
2019 Nov 06
9
[PATCH V10 0/6] mdev based hardware virtio offloading support
...h is a good reference for vendors who is interested in their own virtio datapath offloading product. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific ops out of the common ones for implementing class specific operations over mdev bus. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/11/5/424 [2] https://lkml.org/...
2019 Nov 07
9
[PATCH V11 0/6] mdev based hardware virtio offloading support
...h is a good reference for vendors who is interested in their own virtio datapath offloading product. Consider mdev framework only support VFIO device and driver right now, this series also extend it to support other types. This is done through introducing class id to the device and pairing it with id_talbe claimed by the driver. On top, this seris also decouple device specific ops out of the common ones for implementing class specific operations over mdev bus. Pktgen test was done with virito-net + mvnet loop back device. Please review. [1] https://lkml.org/lkml/2019/11/5/424 [2] https://lkml.org/...