From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH v3 1/3] eal: introduce integer divide through reciprocal
Date: Mon, 4 Sep 2017 14:01:48 +0000 [thread overview]
Message-ID: <C6ECDF3AB251BE4894318F4E4512369782293857@IRSMSX109.ger.corp.intel.com> (raw)
In-Reply-To: <1504442189-4384-1-git-send-email-pbhagavatula@caviumnetworks.com>
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pavan Nikhilesh
> Sent: Sunday, September 3, 2017 1:36 PM
> To: dev@dpdk.org
> Cc: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>;
> stephen@networkplumber.org; Pavan Nikhilesh
> <pbhagavatula@caviumnetworks.com>
> Subject: [dpdk-dev] [PATCH v3 1/3] eal: introduce integer divide through
> reciprocal
>
> In some use cases of integer division, denominator remains constant and
> numerator varies. It is possible to optimize division for such specific
> scenarios.
>
> The librte_sched uses rte_reciprocal to optimize division so, moving it to
> eal/common would allow other libraries and applications to use it.
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> ---
Reviewed-by: Anatoly Burakov <anatoly.burakov@intel.com>
prev parent reply other threads:[~2017-09-04 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-03 12:36 Pavan Nikhilesh
2017-09-03 12:36 ` [dpdk-dev] [PATCH v3 2/3] eal: add u64 bit variant for reciprocal Pavan Nikhilesh
2017-09-04 14:34 ` Burakov, Anatoly
2017-09-04 14:55 ` Pavan Nikhilesh Bhagavatula
2017-09-03 12:36 ` [dpdk-dev] [PATCH v3 3/3] test: add tests for reciprocal based division Pavan Nikhilesh
2017-09-04 9:18 ` Burakov, Anatoly
2017-09-04 9:49 ` Pavan Nikhilesh Bhagavatula
2017-09-04 14:01 ` Burakov, Anatoly [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=C6ECDF3AB251BE4894318F4E4512369782293857@IRSMSX109.ger.corp.intel.com \
--to=anatoly.burakov@intel.com \
--cc=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).