From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/3] eal: move bitmap from lib sched
Date: Thu, 21 Sep 2017 14:03:44 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891267BABEE4B@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1505994622-902-1-git-send-email-pbhagavatula@caviumnetworks.com>
> -----Original Message-----
> From: Pavan Nikhilesh [mailto:pbhagavatula@caviumnetworks.com]
> Sent: Thursday, September 21, 2017 12:50 PM
> To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>;
> stephen@networkplumber.org
> Cc: dev@dpdk.org; Pavan Bhagavatula
> <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH v3 1/3] eal: move bitmap from lib sched
>
> From: Pavan Bhagavatula <pbhagavatula@caviumnetworks.com>
>
> The librte_sched uses rte_bitmap to manage large arrays of bits in an
> optimized method so, moving it to eal/common would allow other libraries
> and applications to use it.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
>
> v3 changes:
> - address review comments
>
> v2 changes:
> - undo rte_bitmap.h cosmetic changes
> - update maintainer info
>
> lib/librte_eal/common/Makefile | 1 +
> lib/{librte_sched => librte_eal/common/include}/rte_bitmap.h | 0
> lib/librte_sched/Makefile | 2 +-
> lib/librte_sched/rte_sched.c | 2 +-
> 4 files changed, 3 insertions(+), 2 deletions(-)
> rename lib/{librte_sched => librte_eal/common/include}/rte_bitmap.h
> (100%)
>
Thanks very much, Pavan!
Series Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
next prev parent reply other threads:[~2017-09-21 14:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-07 14:39 [dpdk-dev] [PATCH 1/2] " Pavan Nikhilesh
2017-09-07 14:39 ` [dpdk-dev] [PATCH 2/2] test: add test for bitmap operations Pavan Nikhilesh
2017-09-20 13:27 ` [dpdk-dev] [PATCH 1/2] eal: move bitmap from lib sched Dumitrescu, Cristian
2017-09-20 13:32 ` Pavan Nikhilesh Bhagavatula
2017-09-20 15:37 ` [dpdk-dev] [PATCH v2 1/3] " Pavan Nikhilesh
2017-09-20 15:37 ` [dpdk-dev] [PATCH v2 2/3] test: add test for bitmap operations Pavan Nikhilesh
2017-09-20 15:37 ` [dpdk-dev] [PATCH v2 3/3] maintainers: add maintainer for bitmap Pavan Nikhilesh
2017-09-20 15:40 ` [dpdk-dev] [PATCH v2 1/3] eal: move bitmap from lib sched Dumitrescu, Cristian
2017-09-20 15:44 ` Pavan Nikhilesh Bhagavatula
2017-09-20 16:39 ` Dumitrescu, Cristian
2017-09-20 17:25 ` Pavan Nikhilesh Bhagavatula
2017-09-21 10:25 ` Dumitrescu, Cristian
2017-09-21 10:38 ` Pavan Nikhilesh Bhagavatula
2017-09-21 11:50 ` [dpdk-dev] [PATCH v3 " Pavan Nikhilesh
2017-09-21 11:50 ` [dpdk-dev] [PATCH v3 2/3] test: add test for bitmap operations Pavan Nikhilesh
2017-09-21 11:50 ` [dpdk-dev] [PATCH v3 3/3] maintainers: add maintainer for bitmap Pavan Nikhilesh
2017-09-21 14:03 ` Dumitrescu, Cristian [this message]
2017-10-12 20:25 ` [dpdk-dev] [PATCH v3 1/3] eal: move bitmap from lib sched Thomas Monjalon
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=3EB4FA525960D640B5BDFFD6A3D891267BABEE4B@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=pbhagavatula@caviumnetworks.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).