From: Thomas Monjalon <thomas@monjalon.net>
To: Suanming Mou <suanmingm@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"amo@semihalf.com" <amo@semihalf.com>,
Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH v4] bitmap: add init with all bits set
Date: Wed, 15 Apr 2020 16:42:52 +0200 [thread overview]
Message-ID: <3431556.3Lj2Plt8kZ@thomas> (raw)
In-Reply-To: <HE1PR05MB3484BFF32847DB09149A2BEACCDB0@HE1PR05MB3484.eurprd05.prod.outlook.com>
15/04/2020 16:22, Suanming Mou:
> Hi Thomas,
>
> Thanks for the update.
>
> From: Thomas Monjalon <thomas@monjalon.net>
> >
> > From: Suanming Mou <suanmingm@mellanox.com>
> >
> > Currently, in the case to use bitmap as resource allocator, after bitmap creation,
> > all the bitmap bits should be set to indicate the bit available. Every time when
> > allocate one bit, search for the set bits and clear it to make it in use.
> >
> > Add a new rte_bitmap_init_with_all_set() function to have a quick fill up the
> > bitmap bits.
> >
> > Comparing with the case create the bitmap as empty and set the bitmap one by
> > one, the new function costs less cycles.
> >
> > Signed-off-by: Suanming Mou <suanmingm@mellanox.com>
> > Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
> Reviewed-by: Suanming Mou <suanmingm@mellanox.com>
> > ---
> >
> > v4:
> > - add experimental tags and comments
> > - move functions near original init function
> > - squash test patch
> > - use "init" word in title
> >
> > v3 updates:
> > 1. Implement individual rte_bitmap_init_with_all_set() function.
> > 2. Add new function to clear the overhead bits.
> >
> > v2 updates:
> > 1. Split the common part to __rte_bitmap_init().
> > 2. Set the slab bits more customized.
Applied, thanks
prev parent reply other threads:[~2020-04-15 14:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 8:21 [dpdk-dev] [PATCH 0/2] bitmap: add create bitmap " Suanming Mou
2020-03-10 8:21 ` [dpdk-dev] [PATCH 1/2] " Suanming Mou
2020-04-03 14:49 ` Andrzej Ostruszka
2020-04-07 6:19 ` Suanming Mou
2020-04-07 15:00 ` Suanming Mou
2020-04-07 17:48 ` Dumitrescu, Cristian
2020-04-08 2:57 ` Suanming Mou
2020-03-10 8:21 ` [dpdk-dev] [PATCH 2/2] test/bitmap: add bitmap create with all bits set case Suanming Mou
2020-03-25 13:25 ` [dpdk-dev] [PATCH 0/2] bitmap: add create bitmap with all bits set Thomas Monjalon
2020-04-02 13:44 ` Suanming Mou
2020-04-08 3:05 ` [dpdk-dev] [PATCH v2 " Suanming Mou
2020-04-08 3:05 ` [dpdk-dev] [PATCH v2 1/2] " Suanming Mou
2020-04-09 14:16 ` Dumitrescu, Cristian
2020-04-10 10:34 ` Suanming Mou
2020-04-10 11:21 ` Dumitrescu, Cristian
2020-04-10 12:30 ` Suanming Mou
2020-04-08 3:05 ` [dpdk-dev] [PATCH v2 2/2] test/bitmap: add bitmap create with all bits set case Suanming Mou
2020-04-10 12:46 ` [dpdk-dev] [PATCH v3 0/2] bitmap: add create bitmap with all bits set Suanming Mou
2020-04-10 12:46 ` [dpdk-dev] [PATCH v3 1/2] " Suanming Mou
2020-04-10 16:04 ` Dumitrescu, Cristian
2020-04-10 12:46 ` [dpdk-dev] [PATCH v3 2/2] test/bitmap: add bitmap create with all bits set case Suanming Mou
2020-04-15 14:15 ` [dpdk-dev] [PATCH v4] bitmap: add init with all bits set Thomas Monjalon
2020-04-15 14:22 ` Suanming Mou
2020-04-15 14:42 ` Thomas Monjalon [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=3431556.3Lj2Plt8kZ@thomas \
--to=thomas@monjalon.net \
--cc=amo@semihalf.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=suanmingm@mellanox.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).