From: Si-Wei Liu <si-wei.liu@oracle.com>
To: Jason Wang <jasowang@redhat.com>, Eli Cohen <elic@nvidia.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lulu@redhat.com
Subject: Re: [PATCH v1] vdpa/mlx5: Restore the hardware used index after change map
Date: Fri, 19 Feb 2021 19:00:00 -0800 [thread overview]
Message-ID: <c3760a4c-5047-8a03-2935-0b9b5a682dbb@oracle.com> (raw)
In-Reply-To: <2330af63-02e2-77fe-255b-c55f01292e80@redhat.com>
On 2/19/2021 6:38 PM, Jason Wang wrote:
>>>
>>>
>>> Right now the value is exposed to userspace via GET_VRING_BASE, so
>>> only last_avail_idx is synced. If we need sync last_used_idx, we
>>> should also sync pending indices which requires more thoughts.
>> Technically it doesn't sound right - crossing the boundary a bit even
>> with simplified form of assumption. But depending on how userspace
>> could make use of this API, it doesn't seem it breaks existing
>> functionality for the moment.
>
>
> I don't get here, maybe you can explain a little bit more?
Please refer to the email I just sent.
https://lore.kernel.org/lkml/033b0806-4037-5755-a1fa-91dbb58bab2e@oracle.com/
-Siwei
prev parent reply other threads:[~2021-02-20 3:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 7:36 [PATCH v1] vdpa/mlx5: Restore the hardware used index after change map Eli Cohen
2021-02-05 3:57 ` Jason Wang
2021-02-05 23:07 ` Si-Wei Liu
2021-02-08 4:27 ` Jason Wang
2021-02-08 6:37 ` Eli Cohen
2021-02-08 9:04 ` Jason Wang
2021-02-08 9:26 ` Michael S. Tsirkin
2021-02-08 10:04 ` Eli Cohen
2021-02-09 3:20 ` Jason Wang
2021-02-09 6:12 ` Eli Cohen
2021-02-09 6:37 ` Jason Wang
2021-02-10 2:30 ` Si-Wei Liu
2021-02-10 3:53 ` Jason Wang
2021-02-10 8:59 ` Si-Wei Liu
2021-02-10 15:45 ` Eli Cohen
2021-02-17 0:25 ` Si-Wei Liu
2021-02-17 6:51 ` Eli Cohen
2021-02-18 4:44 ` Jason Wang
2021-02-18 12:43 ` Si-Wei Liu
2021-02-19 3:10 ` Jason Wang
2021-02-20 2:05 ` Si-Wei Liu
2021-02-20 2:38 ` Jason Wang
2021-02-20 3:00 ` Si-Wei Liu [this message]
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=c3760a4c-5047-8a03-2935-0b9b5a682dbb@oracle.com \
--to=si-wei.liu@oracle.com \
--cc=elic@nvidia.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).