OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [virtio-comment] Re: [virtio] RE: [virtio-comment] proposal: use admin command (and aq) of the device to query config space

> From: virtio-comment@lists.oasis-open.org <virtio-comment@lists.oasis-
> open.org> On Behalf Of Michael S. Tsirkin
> Sent: Wednesday, August 2, 2023 5:09 PM

> > Sure, device config is the real pain point we are trying to solve first.
> >
> > Using cvq for those devices who has it seems the most optimal approach.
> > If we liberate ourselves from single monolithic config space structure and
> move to query device capabilities, resources, configuration, at functionality
> level, life is lot easier.
> > What are your thoughts?
> Splitting transport and device config is exactly what I'm talking about.
> I agree transport should probably be split further - it only made sense for legacy
> so we don't need to spend specification effort on legacy.
> splitting device config would require changes to all devices - I don't see how it's
> worth the effort.

Maybe I was not clear in my idea.
We have canned ourselves as config means _one_ structure.
Due to this thought process, all these transport and things muddy the view.

If one think of functionality-based config, there is no one structure, hence no need to limit ourselves to it.
Taking concrete example,

We have separate commands for,
a. RSS config
b. filters
c. notification coalescing

When you have matching get command, then each functionality grows by their own get command and no need to put in single box of single config structure.

Every device will be able to grow to dynamic need as/if it arise.

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]