All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Danilewicz, MarcinX" <marcinx.danilewicz@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"Singh, Jasvinder" <jasvinder.singh@intel.com>
Cc: "Ajmera, Megha" <megha.ajmera@intel.com>,
	"Liu, Yu Y" <yu.y.liu@intel.com>
Subject: RE: [PATCH v2] sched: enable CMAN at runtime
Date: Tue, 7 Jun 2022 10:40:42 +0000	[thread overview]
Message-ID: <PH0PR11MB5784D2D171DF08AFA38E6D868FA59@PH0PR11MB5784.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM8PR11MB56701437A82F032E498E0852EBDD9@DM8PR11MB5670.namprd11.prod.outlook.com>

Hi Cristian,

Please find answers inline.

<snip>

> > Log: v2 change in rte_sched.h to avoid ABI breakage.

<snip>

Lessons learned, so I have fixed also positioning of this above.

<snip>

 
> > diff --git a/lib/sched/rte_sched.c b/lib/sched/rte_sched.c index
> > ec74bee939..db14934832 100644
> > --- a/lib/sched/rte_sched.c
> > +++ b/lib/sched/rte_sched.c
> 

<snip>

 
> Same comment here: yes, remove the #ifdef ... #endif, but no need to
> change this code fragment, as it sets correctly the s->cman_enabled flag,
> which is then the only flag used by the rest of the code. Again, no need to
> have a CMAN_NONE in the enumeration, as the same is achieved by setting
> params->cman_params to NULL.

Yes, with that approach this is better.

<snip>

> >  	qe->stats.n_pkts_dropped += 1;
> >  	qe->stats.n_bytes_dropped += pkt_len; -#ifdef RTE_SCHED_CMAN
> >  	if (subport->cman_enabled)
> >  		qe->stats.n_pkts_cman_dropped += n_pkts_cman_dropped;
> -#endif  }
> 
> Please don't forget to remove the __rte_unused attribute for the
> n_pkts_cman_dropped in the function parameters, right?

Nice spot. Looks like this was there for some time.

Regards,
Marcin

  reply	other threads:[~2022-06-07 10:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-11 13:53 [PATCH] sched: enable CMAN at runtime Marcin Danilewicz
2022-05-12 13:10 ` [PATCH v2] " Marcin Danilewicz
2022-05-30 11:19   ` Dumitrescu, Cristian
2022-05-30 14:03     ` Danilewicz, MarcinX
2022-06-02  9:57     ` Danilewicz, MarcinX
2022-05-30 11:35   ` Dumitrescu, Cristian
2022-06-07 10:40     ` Danilewicz, MarcinX [this message]
2022-06-08  9:42   ` [PATCH v3] " Marcin Danilewicz
2022-06-08 11:59     ` Dumitrescu, Cristian
2022-06-08 15:29       ` Danilewicz, MarcinX
2022-06-13  9:09     ` [PATCH v4] " Marcin Danilewicz
2022-06-17 11:48       ` Dumitrescu, Cristian
2022-06-20 13:56       ` [PATCH v5] ched: " Marcin Danilewicz
2022-06-20 14:49         ` Dumitrescu, Cristian
2022-06-21  8:20           ` Danilewicz, MarcinX
2022-06-21  8:16         ` [PATCH v6] sched: " Marcin Danilewicz
2022-06-21 13:27           ` Dumitrescu, Cristian
2022-06-22 15:12             ` Danilewicz, MarcinX
2022-07-04  9:19           ` [PATCH v7] " Marcin Danilewicz
2022-07-05 17:05             ` [PATCH v8] " Marcin Danilewicz
2022-07-05 18:00               ` Ajmera, Megha
2022-07-05 22:26                 ` Danilewicz, MarcinX
2022-07-06  8:53               ` Singh, Jasvinder
2022-07-07 13:07                 ` Danilewicz, MarcinX
2022-07-07 16:28                   ` Singh, Jasvinder
2022-07-07 21:22                     ` Danilewicz, MarcinX
2022-07-08 13:14               ` [PATCH v9] " Marcin Danilewicz

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=PH0PR11MB5784D2D171DF08AFA38E6D868FA59@PH0PR11MB5784.namprd11.prod.outlook.com \
    --to=marcinx.danilewicz@intel.com \
    --cc=cristian.dumitrescu@intel.com \
    --cc=dev@dpdk.org \
    --cc=jasvinder.singh@intel.com \
    --cc=megha.ajmera@intel.com \
    --cc=yu.y.liu@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.