From: Xianting Tian <xianting.tian@linux.alibaba.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: mst@redhat.com, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] virtio_ring: remove unnecessary to_vvq call in vring hot path
Date: Mon, 28 Mar 2022 17:13:16 +0800 [thread overview]
Message-ID: <7d0d6b08-321e-2e09-3ced-add916e6f07d@linux.alibaba.com> (raw)
In-Reply-To: <20220328090503.wk5idknhwsbunkjs@sgarzare-redhat>
在 2022/3/28 下午5:05, Stefano Garzarella 写道:
> On Thu, Mar 24, 2022 at 03:33:40PM +0800, Xianting Tian wrote:
>> It passes '_vq' to virtqueue_use_indirect(), which still calls
>> to_vvq to get 'vq', let's directly pass 'vq'. It can avoid
>> unnecessary call of to_vvq in hot path.
>
> It seems reasonable to me.
>
>>
>> Other tiny optimization:
>> Add unlikely to "if (vq->vq.num_free < descs_used).
>
> Better to do this change in another patch.
Thanks for the reply, I will send the patchset, which contains the two
patches, soon.
>
> Thanks,
> Stefano
>
>>
>> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
>> ---
>> drivers/virtio/virtio_ring.c | 10 ++++------
>> 1 file changed, 4 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
>> index 962f1477b1fa..ab6d5f0cb579 100644
>> --- a/drivers/virtio/virtio_ring.c
>> +++ b/drivers/virtio/virtio_ring.c
>> @@ -205,11 +205,9 @@ struct vring_virtqueue {
>>
>> #define to_vvq(_vq) container_of(_vq, struct vring_virtqueue, vq)
>>
>> -static inline bool virtqueue_use_indirect(struct virtqueue *_vq,
>> +static inline bool virtqueue_use_indirect(struct vring_virtqueue *vq,
>> unsigned int total_sg)
>> {
>> - struct vring_virtqueue *vq = to_vvq(_vq);
>> -
>> /*
>> * If the host supports indirect descriptor tables, and we have
>> multiple
>> * buffers, then go indirect. FIXME: tune this threshold
>> @@ -507,7 +505,7 @@ static inline int virtqueue_add_split(struct
>> virtqueue *_vq,
>>
>> head = vq->free_head;
>>
>> - if (virtqueue_use_indirect(_vq, total_sg))
>> + if (virtqueue_use_indirect(vq, total_sg))
>> desc = alloc_indirect_split(_vq, total_sg, gfp);
>> else {
>> desc = NULL;
>> @@ -527,7 +525,7 @@ static inline int virtqueue_add_split(struct
>> virtqueue *_vq,
>> descs_used = total_sg;
>> }
>>
>> - if (vq->vq.num_free < descs_used) {
>> + if (unlikely(vq->vq.num_free < descs_used)) {
>> pr_debug("Can't add buf len %i - avail = %i\n",
>> descs_used, vq->vq.num_free);
>> /* FIXME: for historical reasons, we force a notify here if
>> @@ -1194,7 +1192,7 @@ static inline int virtqueue_add_packed(struct
>> virtqueue *_vq,
>>
>> BUG_ON(total_sg == 0);
>>
>> - if (virtqueue_use_indirect(_vq, total_sg)) {
>> + if (virtqueue_use_indirect(vq, total_sg)) {
>> err = virtqueue_add_indirect_packed(vq, sgs, total_sg, out_sgs,
>> in_sgs, data, gfp);
>> if (err != -ENOMEM) {
>> --
>> 2.17.1
>>
next prev parent reply other threads:[~2022-03-28 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 7:33 Xianting Tian
2022-03-28 9:05 ` Stefano Garzarella
2022-03-28 9:13 ` Xianting Tian [this message]
2022-06-22 8:51 Deming Wang
2022-06-22 9:09 Deming Wang
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=7d0d6b08-321e-2e09-3ced-add916e6f07d@linux.alibaba.com \
--to=xianting.tian@linux.alibaba.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--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
all inboxes | Powered by JetHome®