qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Li Hangjing <lihangjing@baidu.com>,
	Sergio Lopez <slp@redhat.com>,
	qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Chai Wen <chaiwen@baidu.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Xie Yongji <xieyongji@baidu.com>
Subject: Re: [PATCH] virtio-blk: Convert QEMUBH callback to "bitops.h" API
Date: Thu, 6 May 2021 11:22:14 -0700	[thread overview]
Message-ID: <fdf97a71-1359-e186-a895-3383c31ca20c@linaro.org> (raw)
In-Reply-To: <20210506155419.1796056-1-philmd@redhat.com>

On 5/6/21 8:54 AM, Philippe Mathieu-Daudé wrote:
>   static void notify_guest_bh(void *opaque)
>   {
>       VirtIOBlockDataPlane *s = opaque;
> -    unsigned nvqs = s->conf->num_queues;
> -    unsigned long bitmap[BITS_TO_LONGS(nvqs)];
> -    unsigned j;
>   
> -    memcpy(bitmap, s->batch_notify_vqs, sizeof(bitmap));
> -    memset(s->batch_notify_vqs, 0, sizeof(bitmap));
> -
> -    for (j = 0; j < nvqs; j += BITS_PER_LONG) {
> -        unsigned long bits = bitmap[j / BITS_PER_LONG];
> -
> -        while (bits != 0) {
> -            unsigned i = j + ctzl(bits);
> +    for (unsigned i = 0; i < s->conf->num_queues; i++) {

Is this bitmap dense enough that you want to iterate by index, or is it sparse 
enough to iterate via find_first_bit/find_next_bit?

In either case, leave the copy of  s->conf->num_queues to a local variable.


r~


  reply	other threads:[~2021-05-06 18:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 15:54 [PATCH] virtio-blk: Convert QEMUBH callback to "bitops.h" API Philippe Mathieu-Daudé
2021-05-06 18:22 ` Richard Henderson [this message]
2021-05-06 19:42   ` Philippe Mathieu-Daudé
2021-05-06 20:00     ` Philippe Mathieu-Daudé

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=fdf97a71-1359-e186-a895-3383c31ca20c@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=chaiwen@baidu.com \
    --cc=kwolf@redhat.com \
    --cc=lihangjing@baidu.com \
    --cc=mreitz@redhat.com \
    --cc=philmd@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=slp@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=xieyongji@baidu.com \
    /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).