From: "tomorrow Wang (王德明)" <wangdeming@inspur.com>
To: "christophe.jaillet@wanadoo.fr" <christophe.jaillet@wanadoo.fr>,
"mst@redhat.com" <mst@redhat.com>,
"jasowang@redhat.com" <jasowang@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"virtualization@lists.linux-foundation.org"
<virtualization@lists.linux-foundation.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] virtio: Directly use ida_alloc_range()/ida_free()
Date: Thu, 9 Jun 2022 00:42:11 +0000 [thread overview]
Message-ID: <aff7bba2680b49fab6a14694e33fd41d@inspur.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
Hi,
> Hi,
>
> Le 08/06/2022 à 08:08, Deming Wang a écrit :
> > Use ida_alloc_range()/ida_free() instead of deprecated
> > ida_simple_get()/ida_simple_remove() .
> >
> > Signed-off-by: Deming Wang <wangdeming@inspur.com>
> > ---
> > drivers/vhost/vdpa.c | 5 ++---
> > 1 file changed, 2 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/vhost/vdpa.c b/drivers/vhost/vdpa.c index
> > 935a1d0ddb97..384049cfca8d 100644
> > --- a/drivers/vhost/vdpa.c
> > +++ b/drivers/vhost/vdpa.c
> > @@ -1293,7 +1293,7 @@ static void vhost_vdpa_release_dev(struct device
> *device)
> > struct vhost_vdpa *v =
> > container_of(device, struct vhost_vdpa, dev);
> >
> > - ida_simple_remove(&vhost_vdpa_ida, v->minor);
> > + ida_free(&vhost_vdpa_ida, v->minor);
> > kfree(v->vqs);
> > kfree(v);
> > }
> > @@ -1316,8 +1316,7 @@ static int vhost_vdpa_probe(struct vdpa_device
> *vdpa)
> > if (!v)
> > return -ENOMEM;
> >
> > - minor = ida_simple_get(&vhost_vdpa_ida, 0,
> > - VHOST_VDPA_DEV_MAX, GFP_KERNEL);
> > + minor = ida_alloc_range(&vhost_vdpa_ida, 0, VHOST_VDPA_DEV_MAX -
> 1,
> > +GFP_KERNEL);
>
> ida_alloc_max() would be better here. It is less verbose.
>
> An explanation in the commit log of why the -1 is needed would also help
> reviewer/maintainer, IMHO.
>
> It IS correct, but it is not that obvious without looking at
> ida_simple_get() and ida_alloc_range().
>
> CJ
>
>
> > if (minor < 0) {
> > kfree(v);
> > return minor;
can I mention one patch about repair ida_free for this.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 3780 bytes --]
next reply other threads:[~2022-06-09 0:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 0:42 tomorrow Wang (王德明) [this message]
2022-06-09 4:59 ` [PATCH] virtio: Directly use ida_alloc_range()/ida_free() Christophe JAILLET
-- strict thread matches above, loose matches on Subject: below --
2022-06-08 6:14 Deming Wang
2022-06-08 6:08 Deming Wang
2022-06-08 19:06 ` Christophe JAILLET
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=aff7bba2680b49fab6a14694e33fd41d@inspur.com \
--to=wangdeming@inspur.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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