All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Linga, Pavan Kumar" <pavan.kumar.linga@intel.com>
To: Jakub Kicinski <kuba@kernel.org>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: <davem@davemloft.net>, <pabeni@redhat.com>, <edumazet@google.com>,
	<netdev@vger.kernel.org>, <emil.s.tantilov@intel.com>,
	<jesse.brandeburg@intel.com>, <sridhar.samudrala@intel.com>,
	<shiraz.saleem@intel.com>, <sindhu.devale@intel.com>,
	<willemb@google.com>, <decot@google.com>, <andrew@lunn.ch>,
	<leon@kernel.org>, <mst@redhat.com>, <simon.horman@corigine.com>,
	<shannon.nelson@amd.com>, <stephen@networkplumber.org>,
	Alan Brady <alan.brady@intel.com>,
	Joshua Hay <joshua.a.hay@intel.com>,
	Madhu Chittim <madhu.chittim@intel.com>,
	"Phani Burra" <phani.r.burra@intel.com>,
	Shailendra Bhatnagar <shailendra.bhatnagar@intel.com>
Subject: Re: [PATCH net-next v2 04/15] idpf: add core init and interrupt request
Date: Wed, 21 Jun 2023 12:07:35 -0700	[thread overview]
Message-ID: <bca91094-f349-30e1-7835-80a5069c2ca4@intel.com> (raw)
In-Reply-To: <20230616235041.4d3f99fe@kernel.org>



On 6/16/2023 11:50 PM, Jakub Kicinski wrote:
> On Wed, 14 Jun 2023 10:14:17 -0700 Tony Nguyen wrote:
>> + * @IDPF_REL_RES_IN_PROG: Resources release in progress
> 
>> + * @IDPF_CANCEL_SERVICE_TASK: Do not schedule service task if bit is set
>> + * @IDPF_REMOVE_IN_PROG: Driver remove in progress
> 
> Why all the X-in-progress flags, again?
> 

IDPF_REMOVE_IN_PROG is used for the conditional checks to indicate that 
the rmmod is in progress and there is no scope to process any hardware 
resets if the bit is set.

IDPF_HR_RESET_IN_PROG is used on hardware reset to not send any 
statistics message to the device Control Plane and to avoid releasing 
the configured netdevs if the bit is set.

After taking a deeper look, IDPF_REL_RES_IN_PROG does not serve the 
purpose as IDPF_REMOVE_IN_PROG already takes care of it. Will cleanup 
this flag.

>> +	set_bit(IDPF_CANCEL_SERVICE_TASK, adapter->flags);
>> +	cancel_delayed_work_sync(&adapter->serv_task);
>> +	clear_bit(IDPF_CANCEL_SERVICE_TASK, adapter->flags);
> 
> Pretty sure workqueue protects from self-requeueing.

Agree with you. Will remove both CANCEL_STATS_TASK and 
CANCEL_SERVICE_TASK flags.

Thanks,
Pavan

  reply	other threads:[~2023-06-21 19:07 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 17:14 [PATCH net-next v2 00/15][pull request] Introduce Intel IDPF driver Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 01/15] virtchnl: add virtchnl version 2 ops Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 02/15] idpf: add module register and probe functionality Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 03/15] idpf: add controlq init and reset checks Tony Nguyen
2023-06-17  6:42   ` Jakub Kicinski
2023-06-21 19:05     ` Linga, Pavan Kumar
2023-06-21 19:14       ` Jakub Kicinski
2023-06-21 19:43         ` Simon Horman
2023-06-14 17:14 ` [PATCH net-next v2 04/15] idpf: add core init and interrupt request Tony Nguyen
2023-06-17  6:50   ` Jakub Kicinski
2023-06-21 19:07     ` Linga, Pavan Kumar [this message]
2023-06-14 17:14 ` [PATCH net-next v2 05/15] idpf: add create vport and netdev configuration Tony Nguyen
2023-06-14 18:21   ` Stephen Hemminger
2023-06-15  0:12     ` Linga, Pavan Kumar
2023-06-14 17:14 ` [PATCH net-next v2 06/15] idpf: continue expanding init task Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 07/15] idpf: configure resources for TX queues Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 08/15] idpf: configure resources for RX queues Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 09/15] idpf: initialize interrupts and enable vport Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 10/15] idpf: add splitq start_xmit Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 11/15] idpf: add TX splitq napi poll support Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 12/15] idpf: add RX " Tony Nguyen
2023-06-17  6:55   ` Jakub Kicinski
2023-06-21 19:07     ` Linga, Pavan Kumar
2023-06-17  7:01   ` Jakub Kicinski
2023-06-21 19:09     ` Linga, Pavan Kumar
2023-06-21 19:21       ` Jakub Kicinski
2023-06-14 17:14 ` [PATCH net-next v2 13/15] idpf: add singleq start_xmit and napi poll Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 14/15] idpf: add ethtool callbacks Tony Nguyen
2023-06-14 17:14 ` [PATCH net-next v2 15/15] idpf: configure SRIOV and add other ndo_ops Tony Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2023-04-11  1:13 [PATCH net-next v2 00/15] Introduce Intel IDPF driver Pavan Kumar Linga
2023-04-11  1:13 ` [PATCH net-next v2 04/15] idpf: add core init and interrupt request Pavan Kumar Linga
2023-04-11  9:52   ` Simon Horman
2023-04-13 19:10     ` Tantilov, Emil S

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=bca91094-f349-30e1-7835-80a5069c2ca4@intel.com \
    --to=pavan.kumar.linga@intel.com \
    --cc=alan.brady@intel.com \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=davem@davemloft.net \
    --cc=decot@google.com \
    --cc=edumazet@google.com \
    --cc=emil.s.tantilov@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=joshua.a.hay@intel.com \
    --cc=kuba@kernel.org \
    --cc=leon@kernel.org \
    --cc=madhu.chittim@intel.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=phani.r.burra@intel.com \
    --cc=shailendra.bhatnagar@intel.com \
    --cc=shannon.nelson@amd.com \
    --cc=shiraz.saleem@intel.com \
    --cc=simon.horman@corigine.com \
    --cc=sindhu.devale@intel.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=stephen@networkplumber.org \
    --cc=willemb@google.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.