Re: RFC: VDPA Interrupt vector distribution

Hi Eli:

On Mon, Jan 23, 2023 at 1:59 PM Eli Cohen [off-list ref] wrote:

VDPA allows hardware drivers the propagate interrupts from the hardware
directly to the vCPU used by the guest. In a typical implementation, the
hardware driver will assign the interrupt vectors to the virtqueues and report
this information back through the get_vq_irq() callback defined in
struct vdpa_config_ops.

Interrupt vectors could be a scarce resource and may be limited. For such
cases, we can opt the administrator, through the vdpa tool, to set the policy
defining how to distribute the available vectors amongst the data virtqueues.

The following policies are proposed:

1. First comes first served. Assign a vector to each data virtqueue by the
    virtqueue index. Virtqueues which could not be assigned a dedicated vector
    would use the hardware driver to propagate interrupts using the available
    callback mechanism.

    vdpa dev add name vdpa0 mgmtdev pci/0000:86:00.2 int=all

    This is the default mode and works even if "int=all" was not specified.

2. Use round robin distribution so virtqueues could share vectors.
    vdpa dev add name vdpa0 mgmtdev pci/0000:86:00.2 int=all intmode=share

3. Assign vectors to RX virtqueues only.
3.1 Do not share vectors
     vdpa dev add name vdpa0 mgmtdev pci/0000:86:00.2 int=rx
3.2 Share vectors
     vdpa dev add name vdpa0 mgmtdev pci/0000:86:00.2 int=rx intmode=share

4. Assign vectors to TX virtqueues only. Can share or not, like rx.
5. Fail device creation if number of vectors cannot be fulfilled.
    vdpa dev add name vdpa0 mgmtdev pci/0000:86:00.2 max_vq_pairs 8 int=rx intnum=8

I wonder:

1) how the administrator can know if there's sufficient resources for
one of the above policies.
2) how does the administrator know which policy is the best assuming
the resources are sufficient? (E.g vectors to RX only or vectors to TX
only)

If it requires a vendor specific way or knowledge, I believe it's
better to code them in:

1) the vDPA parent or
2) underlayer management tool or drivers

Thanks

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization