All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Penigalapati, Sandeep" <sandeep.penigalapati@intel.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"kuba@kernel.org" <kuba@kernel.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"kernel-janitors@vger.kernel.org"
	<kernel-janitors@vger.kernel.org>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [Intel-wired-lan] [PATCH] ice: Slightly simply ice_find_free_recp_res_idx
Date: Thu, 6 Jan 2022 04:47:00 +0000	[thread overview]
Message-ID: <MW3PR11MB4554704CA84792B1E75110E69C4C9@MW3PR11MB4554.namprd11.prod.outlook.com> (raw)
In-Reply-To: <dc5cd04eed7dd3100f5860acaa995efa40ddecc8.1637183999.git.christophe.jaillet@wanadoo.fr>

>-----Original Message-----
>From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
>Christophe JAILLET
>Sent: Thursday, November 18, 2021 2:51 AM
>To: Brandeburg, Jesse <jesse.brandeburg@intel.com>; Nguyen, Anthony L
><anthony.l.nguyen@intel.com>; davem@davemloft.net; kuba@kernel.org
>Cc: netdev@vger.kernel.org; kernel-janitors@vger.kernel.org; Christophe
>JAILLET <christophe.jaillet@wanadoo.fr>; intel-wired-lan@lists.osuosl.org;
>linux-kernel@vger.kernel.org
>Subject: [Intel-wired-lan] [PATCH] ice: Slightly simply
>ice_find_free_recp_res_idx
>
>The 'possible_idx' bitmap is set just after it is zeroed, so we can save the first
>step.
>
>The 'free_idx' bitmap is used only at the end of the function as the result of a
>bitmap xor operation. So there is no need to explicitly zero it before.
>
>So, slightly simply the code and remove 2 useless 'bitmap_zero()' call
>
>Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>---
>I don't think it will make any differences in RL. ICE_MAX_FV_WORDS is just 48
>(bits), so 1 or 2 longs
>---
> drivers/net/ethernet/intel/ice/ice_switch.c | 2 --
> 1 file changed, 2 deletions(-)
>
Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>

WARNING: multiple messages have this Message-ID (diff)
From: Penigalapati, Sandeep <sandeep.penigalapati@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH] ice: Slightly simply ice_find_free_recp_res_idx
Date: Thu, 6 Jan 2022 04:47:00 +0000	[thread overview]
Message-ID: <MW3PR11MB4554704CA84792B1E75110E69C4C9@MW3PR11MB4554.namprd11.prod.outlook.com> (raw)
In-Reply-To: <dc5cd04eed7dd3100f5860acaa995efa40ddecc8.1637183999.git.christophe.jaillet@wanadoo.fr>

>-----Original Message-----
>From: Intel-wired-lan <intel-wired-lan-bounces@osuosl.org> On Behalf Of
>Christophe JAILLET
>Sent: Thursday, November 18, 2021 2:51 AM
>To: Brandeburg, Jesse <jesse.brandeburg@intel.com>; Nguyen, Anthony L
><anthony.l.nguyen@intel.com>; davem at davemloft.net; kuba at kernel.org
>Cc: netdev at vger.kernel.org; kernel-janitors at vger.kernel.org; Christophe
>JAILLET <christophe.jaillet@wanadoo.fr>; intel-wired-lan at lists.osuosl.org;
>linux-kernel at vger.kernel.org
>Subject: [Intel-wired-lan] [PATCH] ice: Slightly simply
>ice_find_free_recp_res_idx
>
>The 'possible_idx' bitmap is set just after it is zeroed, so we can save the first
>step.
>
>The 'free_idx' bitmap is used only at the end of the function as the result of a
>bitmap xor operation. So there is no need to explicitly zero it before.
>
>So, slightly simply the code and remove 2 useless 'bitmap_zero()' call
>
>Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
>---
>I don't think it will make any differences in RL. ICE_MAX_FV_WORDS is just 48
>(bits), so 1 or 2 longs
>---
> drivers/net/ethernet/intel/ice/ice_switch.c | 2 --
> 1 file changed, 2 deletions(-)
>
Tested-by: Sandeep Penigalapati <sandeep.penigalapati@intel.com>

  reply	other threads:[~2022-01-06  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17 21:21 [PATCH] ice: Slightly simply ice_find_free_recp_res_idx Christophe JAILLET
2021-11-17 21:21 ` [Intel-wired-lan] " Christophe JAILLET
2022-01-06  4:47 ` Penigalapati, Sandeep [this message]
2022-01-06  4:47   ` Penigalapati, Sandeep

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=MW3PR11MB4554704CA84792B1E75110E69C4C9@MW3PR11MB4554.namprd11.prod.outlook.com \
    --to=sandeep.penigalapati@intel.com \
    --cc=anthony.l.nguyen@intel.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=davem@davemloft.net \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jesse.brandeburg@intel.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.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 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.