public inbox for virtio-comment@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexander Gordeev <quic_agordeev@quicinc.com>
To: Parav Pandit <parav@nvidia.com>,
	"virtio-comment@lists.linux.dev" <virtio-comment@lists.linux.dev>
Cc: Trilok Soni <quic_tsoni@quicinc.com>,
	Srivatsa Vaddagiri <quic_svaddagi@quicinc.com>
Subject: Re: virtio-video device IDs
Date: Fri, 27 Dec 2024 12:15:44 +0100	[thread overview]
Message-ID: <eb8370fe-a4df-4a36-a2b6-e9f2bef9fab1@quicinc.com> (raw)
In-Reply-To: <CY8PR12MB71957E005C26FEC6CDE7170FDC012@CY8PR12MB7195.namprd12.prod.outlook.com>

On 22/12/2024 15:14, Parav Pandit wrote:
>> From: Alexander Gordeev <quic_agordeev@quicinc.com>
>> Sent: Friday, December 20, 2024 10:17 PM
>>
>> Hi,
>>
>> Currently there are two device IDs assigned for the future virtio video device:
>>  * 30 for the encoder
>>  * 31 for the decoder
>> I received feedback from our internal reviewers that in some cases it would
>> be better to use as few virtqueues as possible. So if a single piece of HW
>> supports both encoder and decoder functions, then it is better to have a
>> single virtual device, that provides both functions as well. The specific
>> function can be selected per stream then.
>> Is it OK to make changes to the reserved IDs?
>> Are there any other concerns?
>>
>> Thanks
> 
> For the new device usually, there is a new device id.
> May be you can explore how to merge the functionality using capabilities or feature bits to 
> a. either extend encoder to have additional decoder
> or
> b. extend decoded to have the encoder
> 
> and than the description can be changed.
> 
> Or 
> c. if the new device has major functionality and performance, may be its own.
> 
> I believe the details would be useful to find the suitable option from the 3 choices.

I don't understand option 3. Perhaps there are typos.
At the moment I think we'll choose option 1. Thanks!

  reply	other threads:[~2024-12-27 11:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-20 16:47 virtio-video device IDs Alexander Gordeev
2024-12-22 14:14 ` Parav Pandit
2024-12-27 11:15   ` Alexander Gordeev [this message]
2024-12-23 10:57 ` Michael S. Tsirkin
2024-12-27 11:14   ` Alexander Gordeev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=eb8370fe-a4df-4a36-a2b6-e9f2bef9fab1@quicinc.com \
    --to=quic_agordeev@quicinc.com \
    --cc=parav@nvidia.com \
    --cc=quic_svaddagi@quicinc.com \
    --cc=quic_tsoni@quicinc.com \
    --cc=virtio-comment@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox