From: 王志宏 <wangzhihong.wzh@bytedance.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, anatoly.burakov@intel.com, qi.z.zhang@intel.com
Subject: Re: [External] Re: [PATCH] eal/linux: register mp hotplug callback after memory init
Date: Thu, 8 Jun 2023 02:29:25 -0500 [thread overview]
Message-ID: <CAMne5nAbU_gxWK3YH6JXo73buPghnNc=PMZjLVat5tSL0+zNTA@mail.gmail.com> (raw)
In-Reply-To: <CAJFAV8z=vTDWUzm=t6iaNdQS=8Tkt8TCyaGTsfFM6ab94EVbMA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 682 bytes --]
Done. Thanks :)
From: "David Marchand"<david.marchand@redhat.com>
Date: Thu, Jun 8, 2023, 04:21
Subject: [External] Re: [PATCH] eal/linux: register mp hotplug callback
after memory init
To: "Zhihong Wang"<wangzhihong.wzh@bytedance.com>
Cc: <dev@dpdk.org>, <anatoly.burakov@intel.com>, <qi.z.zhang@intel.com>
Hello Zhihong,
On Wed, May 31, 2023 at 8:55 AM Zhihong Wang
<wangzhihong.wzh@bytedance.com> wrote:
>
> Secondary would crash if it tries to handle mp requests before memory
> init, since globals such as eth_dev_shared_data_lock are not accessible
> to it at this moment.
Can you please resend this patch with a SoB ?
Thanks.
--
David Marchand
[-- Attachment #2: Type: text/html, Size: 4807 bytes --]
next prev parent reply other threads:[~2023-06-08 7:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 6:55 Zhihong Wang
2023-06-01 12:26 ` Burakov, Anatoly
2023-06-02 3:33 ` [External] " 王志宏
2023-06-02 13:10 ` Burakov, Anatoly
2023-06-02 13:10 ` Burakov, Anatoly
2023-06-07 20:21 ` David Marchand
2023-06-08 7:29 ` 王志宏 [this message]
2023-06-08 7:25 ` [PATCH v2] " Zhihong Wang
2023-06-08 8:08 ` David Marchand
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='CAMne5nAbU_gxWK3YH6JXo73buPghnNc=PMZjLVat5tSL0+zNTA@mail.gmail.com' \
--to=wangzhihong.wzh@bytedance.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).