From: Thomas Monjalon <thomas@monjalon.net>
To: "Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: dev@dpdk.org, "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Subject: Re: [dpdk-dev] [PATCH] doc: add meter API change to release notes
Date: Fri, 06 Apr 2018 18:51:51 +0200 [thread overview]
Message-ID: <1695939.d5zgjGaqM5@xps> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BB3B5F8@IRSMSX108.ger.corp.intel.com>
05/04/2018 14:03, Dumitrescu, Cristian:
> From: Singh, Jasvinder
> >
> > Update the release notes with meter api change to support configuration
> > profiles.
> >
> > Signed-off-by: Jasvinder Singh <jasvinder.singh@intel.com>
> > ---
> > --- a/doc/guides/rel_notes/release_18_05.rst
> > +++ b/doc/guides/rel_notes/release_18_05.rst
> > @@ -72,6 +72,16 @@ API Changes
> > Also, make sure to start the actual text at the margin.
> > =========================================================
> >
> > +* **Meter API updated to accomodate configuration profiles.**
> > +
> > + The meter API is changed to support meter configuration profiles. The
> > + configuration profile represents the set of configuration parameters
> > + for a given meter object, such as the rates and sizes for the token
> > + buckets. These configuration parameters were previously the part of
> > meter
> > + object internal data strcuture. The separation of the configuration
> > + parameters from meter object data structure results in reducing its
> > + memory footprint which helps in better cache utilization when large
> > number
> > + of meter objects are used.
>
> Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Applied with a small formatting change:
* meter: updated to accommodate configuration profiles.
prev parent reply other threads:[~2018-04-06 16:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 11:49 Jasvinder Singh
2018-04-05 12:03 ` Dumitrescu, Cristian
2018-04-06 16:51 ` 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=1695939.d5zgjGaqM5@xps \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@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 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).