All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Wei Hu <weh@microsoft.com>
Cc: Wei Hu <weh@linux.microsoft.com>, "dev@dpdk.org" <dev@dpdk.org>,
	Long Li <longli@microsoft.com>
Subject: Re: [EXTERNAL] Re: [PATCH v3 0/2] net/mana: add device reset support
Date: Thu, 28 May 2026 11:24:40 -0700	[thread overview]
Message-ID: <20260528112440.3f7e25cc@phoenix.local> (raw)
In-Reply-To: <SE3P153MB18483B2B0A91A49747176C88BB092@SE3P153MB1848.APCP153.PROD.OUTLOOK.COM>

On Thu, 28 May 2026 07:30:03 +0000
Wei Hu <weh@microsoft.com> wrote:

> >    so they are invisible to rte_rcu_qsbr_check in the primary, and
> >    the secondary MP handler (mana_mp_reset_enter) does not call
> >    qsbr_check at all -- it just sets db_page = NULL and munmaps.
> > 
> >    The dev_state check at the top of secondary tx_burst is racy:
> >    the page can be munmapped after the in-loop read of db_page but
> >    before the doorbell write at the bottom.  The "All secondary
> >    threads are quiescent" log line in mana_mp_reset_enter is not
> >    true.
> > 
> >    The secondary needs a real reader-side primitive -- its own
> >    qsbr with secondary lcore registration, or an rwlock the MP
> >    handler takes before munmap.
> >   
> 
> Thanks for the v3 review, @Stephen. I will send out v4 to incorporate most
> of the review comments except for this one. 
> 
> The review on this point is not correct. Here I am providing analysis from
>  AI and my own test results to show why.
> 
> The concern is that "rte_rcu_qsbr_thread_register is only called
> from mana_dev_configure, which the secondary never runs", so
> secondary tids are unregistered and invisible to rte_rcu_qsbr_check.


Thanks, I have become way to familiar with AI reaching false conclusions.

      reply	other threads:[~2026-05-28 18:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-22  6:59 [PATCH v3 0/2] net/mana: add device reset support Wei Hu
2026-05-22  6:59 ` [PATCH v3 1/2] " Wei Hu
2026-05-22  6:59 ` [PATCH v3 2/2] net/mana: add documentation for " Wei Hu
2026-05-26 19:37 ` [PATCH v3 0/2] net/mana: add " Stephen Hemminger
2026-05-28  7:30   ` [EXTERNAL] " Wei Hu
2026-05-28 18:24     ` Stephen Hemminger [this message]

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=20260528112440.3f7e25cc@phoenix.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=longli@microsoft.com \
    --cc=weh@linux.microsoft.com \
    --cc=weh@microsoft.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.