Netdev List
 help / color / mirror / Atom feed
From: Satish Kharat <satishkh@cisco.com>
To: netdev-bot+sashiko@kernel.org
Cc: netdev@vger.kernel.org, sebaddel@cisco.com, aradhana@cisco.com,
	rfaucett@cisco.com, andrew+netdev@lunn.ch, davem@davemloft.net,
	edumazet@kernel.org, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH net v5 1/2] enic: retain admin-channel DMA until queues stop
Date: Sat,  7 Nov 2026 09:59:00 -0800	[thread overview]
Message-ID: <20261107175900.1141309-1-satishkh@cisco.com> (raw)
In-Reply-To: <179406378503.994134.16615988654708205370@kernel.org>

Thanks for the review.

I agree that the reset-worker comments no longer describe every close
outcome. V6 will say that admin close releases the DMA resources only
when both queues report stopped; otherwise it quarantines the channel
and the reset is abandoned.

The failed internal enic_open() lifecycle issue is pre-existing and is
separate from admin DMA ownership. I will address it in a separate patch
with a consistent datapath lifecycle fix. That work will fault-inject
the enic_open() failure points and then exercise administrative close and
device removal, rather than adding a partial datapath-state fix to this
series.

  reply	other threads:[~2026-11-07 17:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-03 12:36 [PATCH net v5 0/2] enic: retain admin DMA resources and identify V2 VFs Satish Kharat
2026-11-03 12:36 ` [PATCH net v5 1/2] enic: retain admin-channel DMA until queues stop Satish Kharat
2026-11-07 15:03   ` netdev-bot+sashiko
2026-11-07 17:59     ` Satish Kharat [this message]
2026-11-03 12:36 ` [PATCH net v5 2/2] enic: require DEVCMD2 and set the V2 VF mailbox source Satish Kharat
2026-11-07 15:03   ` netdev-bot+sashiko
2026-11-07 17:59     ` Satish Kharat

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=20261107175900.1141309-1-satishkh@cisco.com \
    --to=satishkh@cisco.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=aradhana@cisco.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=kuba@kernel.org \
    --cc=netdev-bot+sashiko@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rfaucett@cisco.com \
    --cc=sebaddel@cisco.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