From: Thomas Monjalon <thomas@monjalon.net>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, "Dumitrescu,
Cristian" <cristian.dumitrescu@intel.com>,
"Krakowiak, LukaszX" <lukaszx.krakowiak@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] sched: modify internal structs and functions for 64 bit values
Date: Fri, 25 Oct 2019 18:08:37 +0200 [thread overview]
Message-ID: <1730211.nGpjPk5n0j@xps> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891268E946FC5@IRSMSX108.ger.corp.intel.com>
16/10/2019 17:14, Dumitrescu, Cristian:
> From: Singh, Jasvinder
> >
> > Modify internal structure and functions to support 64-bit
> > values for rates and stats parameters.
> >
> > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> > Signed-off-by: Lukasz Krakowiak <lukaszx.krakowiak@intel.com>
> > ---
> > v2:
> > - remove rte_sched_min_val_2_u32() from rte_sched_common.h
> > - replace rte_sched_min_val_2_u32() by RTE_MIN in rte_sched.c
> > - replace sched_counter_t by uint64_t
> > - add 64 bit version of rte_approx
> >
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-10-25 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 17:24 [dpdk-dev] [PATCH 1/2] sched: add support for 64 bit values Jasvinder Singh
2019-10-14 17:24 ` [dpdk-dev] [PATCH 2/2] sched: modify internal structs and functions " Jasvinder Singh
2019-10-15 15:47 ` Dumitrescu, Cristian
2019-10-15 16:01 ` Singh, Jasvinder
2019-10-15 15:27 ` [dpdk-dev] [PATCH 1/2] sched: add support " Dumitrescu, Cristian
2019-10-16 14:17 ` [dpdk-dev] [PATCH v2 " Jasvinder Singh
2019-10-16 14:17 ` [dpdk-dev] [PATCH v2 2/2] sched: modify internal structs and functions " Jasvinder Singh
2019-10-16 15:14 ` Dumitrescu, Cristian
2019-10-25 16:08 ` 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=1730211.nGpjPk5n0j@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=lukaszx.krakowiak@intel.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.