From: Stephen Hemminger <stephen@networkplumber.org>
To: Vivek Sharma <vivek.sharma@caviumnetworks.com>
Cc: dev@dpdk.org, cristian.dumitrescu@intel.com
Subject: Re: [dpdk-dev] [PATCH 0/2] eal/bitmap: support reverse bitmap scan
Date: Sun, 11 Jun 2023 19:23:02 -0700 [thread overview]
Message-ID: <20230611192302.508375be@hermes.local> (raw)
In-Reply-To: <1539071699-29963-1-git-send-email-vivek.sharma@caviumnetworks.com>
On Tue, 9 Oct 2018 13:24:57 +0530
Vivek Sharma <vivek.sharma@caviumnetworks.com> wrote:
> This patchset implements the support for reverse bitmap scanning along with
> test support. Reverse scanning is quite useful when bit position signifies
> an ordering according to some attribute, e.g., priority ordering.
>
> Prerequisite:
> * Note that this patchset is dependent on patch:-
> 'http://patches.dpdk.org/patch/45307/'
>
> Vivek Sharma (2):
> eal/bitmap: support bitmap reverse scanning
> test/bitmap: implement reverse bitmap scan test
>
> lib/librte_eal/common/include/rte_bitmap.h | 164 +++++++++++++++++++++++++----
> test/test/test_bitmap.c | 71 ++++++++++++-
> 2 files changed, 213 insertions(+), 22 deletions(-)
>
This patchset has had no feedback in 5 years.
* There was never an application that needed it.
* EAL directory structure changed.
* It would cause an ABI breakage.
If you have an example that needs it, then rebase and follow ABI
rules and the next ABI change will be for 23.11
prev parent reply other threads:[~2023-06-12 2:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-09 7:54 [PATCH 0/2] eal/bitmap: support reverse bitmap scan Vivek Sharma
2018-10-09 7:54 ` [PATCH 1/2] eal/bitmap: support bitmap reverse scanning Vivek Sharma
2018-10-09 7:54 ` [PATCH 2/2] test/bitmap: implement reverse bitmap scan test Vivek Sharma
2023-06-12 2:23 ` Stephen Hemminger [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=20230611192302.508375be@hermes.local \
--to=stephen@networkplumber.org \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=vivek.sharma@caviumnetworks.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.