search for: vhost_get_work

...> I can spin another patchset with the single ioctl design so we can compare. > So I'm fine with this approach. One last question, I see this: > > /* By default, a device gets one vhost_worker that its virtqueues share. This */ > > I'm wondering if it is better to have a vhost_get_worker() to return > the worker_id of a specific queue. In the future, this might be useful > for devices that have multiple workers by default? Yeah, it would be useful. Just 2 questions. You mean an ioctl command to get this info right? I had added one in one version a while back, but dropped i...

...patchset with the single ioctl design so we can compare. > > So I'm fine with this approach. One last question, I see this: > > > > /* By default, a device gets one vhost_worker that its virtqueues share. This */ > > > > I'm wondering if it is better to have a vhost_get_worker() to return > > the worker_id of a specific queue. In the future, this might be useful > > for devices that have multiple workers by default? > > Yeah, it would be useful. Just 2 questions. You mean an ioctl command to get > this info right? I had added one in one version a w...

...e design. I see. > > I can spin another patchset with the single ioctl design so we can compare. So I'm fine with this approach. One last question, I see this: /* By default, a device gets one vhost_worker that its virtqueues share. This */ I'm wondering if it is better to have a vhost_get_worker() to return the worker_id of a specific queue. In the future, this might be useful for devices that have multiple workers by default? Thanks >