> From: Michael S. Tsirkin <m...@redhat.com> > Sent: Sunday, February 12, 2023 4:42 AM > > On Sat, Feb 11, 2023 at 06:49:52PM +0000, Parav Pandit wrote: > > > > > From: Michael S. Tsirkin <m...@redhat.com> > > > Sent: Thursday, February 9, 2023 7:13 AM > > > > [..] > > > > > My intent is to try and support both SR-IOV and SIOV usecases with > > > the same structure and maybe even the same VQ. > > > > > Probably it is implicit, but is better for us to mention few examples > > use cases here something like, > > > > Admin queue is an infrastructure to support use cases like: > > a. SIOV devices life cycles management (create, destroy, query, > > configure) b. SR-IOV VF device/resource management (SR-PCIM) c. May be > > transport > > > > > For example, it might make sense to split creating/destroying SIOV > > > devices from the transport passing data from the guest - the driver > > > would then not negotiate VIRTIO_F_SR_IOV (which then means auto- > provisioning). > > > > Above intermixing of SIOV and SR_IOV is very confusing. > > Can you please drop it and have simpler examples like above? > > You mean in the cover letter? The more info in the cover letter the better, > this > stuff does not end up in git. Yes, in the cover letter. Its ok its not in the git. Maybe we can start also in the git. Sometimes it's useful for series like this. it is easy to review and digest the use of new feature introduction when those use cases are described in cover letter.
> I'll add your examples too though, thanks! Ok thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
