From: Thomas Monjalon <thomas@monjalon.net>
To: "Dharmappa, Savinay" <savinay.dharmappa@intel.com>,
"Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] sched : Initialize tc ov watermark.
Date: Tue, 20 Apr 2021 15:54:37 +0200 [thread overview]
Message-ID: <2422637.nJklHjyONp@thomas> (raw)
In-Reply-To: <CY4PR1101MB2134B8A04C22900B91BE7EF4E0489@CY4PR1101MB2134.namprd11.prod.outlook.com>
20/04/2021 12:36, Singh, Jasvinder:
> From: Thomas Monjalon <thomas@monjalon.net>
> >
> > Ping
> >
> > 23/03/2021 17:02, Thomas Monjalon:
> > > 09/03/2021 17:10, Savinay Dharmappa:
> > > > tc ov watermark is initialized with computed value of max tc ov
> > > > watermark.
> > >
> > > Sorry I don't understand what the change is doing.
> > > Was there an issue?
> > >
> > > In the title, please avoid "tc ov" which is meaningless for most of
> > > readers I guess.
> >
> >
> Hi Thomas,
>
> This is a fix for oversubscription threshold value of traffic class which is computed later. We will re-spin the patch by mentioning "fix" in the message and title.
Yes please give a clear explanation with full words, thanks.
next prev parent reply other threads:[~2021-04-20 13:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-09 16:01 [dpdk-dev] [PATCH v1] " Savinay Dharmappa
2021-03-09 16:10 ` [dpdk-dev] [PATCH v2] " Savinay Dharmappa
2021-03-10 16:53 ` Singh, Jasvinder
2021-03-15 16:42 ` Coyle, David
2021-03-23 16:02 ` Thomas Monjalon
2021-04-20 10:13 ` Thomas Monjalon
2021-04-20 10:36 ` Singh, Jasvinder
2021-04-20 13:54 ` Thomas Monjalon [this message]
2021-04-21 6:50 ` [dpdk-dev] [PATCH v3] sched : fix traffic class oversubscription parameter Savinay Dharmappa
2021-04-21 14:53 ` Thomas Monjalon
2021-04-21 15:24 ` Dumitrescu, Cristian
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=2422637.nJklHjyONp@thomas \
--to=thomas@monjalon.net \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=jasvinder.singh@intel.com \
--cc=savinay.dharmappa@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).