search for: vring_desc_f_mor

...descriptors: > > virtio 1.0 allows passing a batch of descriptors in both directions, by incrementing > the used/avail index by values > 1. > At the moment only batching of used descriptors is used. > > We can support this by chaining a list of device descriptors through > VRING_DESC_F_MORE flag. Device sets this bit to signal driver that this is part of > a batch of used descriptors which are all part of a single transaction. It supposes each s/g chain represents for a packet, while each descriptor among batching chain represents for a packet. There're a few thoughts of batc...

This is an update from v1 version. Changes: - update event suppression mechanism - separate options for indirect and direct s/g - lots of new features --- Performance analysis of this is in my kvm forum 2016 presentation. The idea is to have a r/w descriptor in a ring structure, replacing the used and available ring, index and descriptor buffer. * Descriptor ring: Guest adds descriptors with

This is an update from v1 version. Changes: - update event suppression mechanism - separate options for indirect and direct s/g - lots of new features --- Performance analysis of this is in my kvm forum 2016 presentation. The idea is to have a r/w descriptor in a ring structure, replacing the used and available ring, index and descriptor buffer. * Descriptor ring: Guest adds descriptors with

...g descriptors: > > virtio 1.0 allows passing a batch of descriptors in both directions, by > incrementing the used/avail index by values > 1. > At the moment only batching of used descriptors is used. > > We can support this by chaining a list of device descriptors through > VRING_DESC_F_MORE flag. Device sets this bit to signal > driver that this is part of a batch of used descriptors > which are all part of a single transaction. If this is a part of a single transaction, I don't see obvious different with DESC_F_NEXT?). I thought for batching, each descriptor is independ...