From: Huichao Cai <chcchc88@163.com>
To: kirankumark@marvell.com
Cc: dev@dpdk.org, jerinj@marvell.com, ndabilpuram@marvell.com,
rjarry@redhat.com, yanzhirun_163@163.com
Subject: Re: [PATCH v2 2/3] graph: add support for node free API
Date: Mon, 11 Nov 2024 17:02:27 +0800 [thread overview]
Message-ID: <1731315747-7335-1-git-send-email-chcchc88@163.com> (raw)
In-Reply-To: <20241111073437.1796101-2-kirankumark@marvell.com>
Do these newly added functions need to protect the linked list with spin lock graph_stpinlock_lock?
next prev parent reply other threads:[~2024-11-11 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 7:34 [PATCH v2 1/3] graph: avoid global node ID counter kirankumark
2024-11-11 7:34 ` [PATCH v2 2/3] graph: add support for node free API kirankumark
2024-11-11 9:02 ` Huichao Cai [this message]
2024-11-11 9:21 ` Huichao Cai
2024-11-11 7:34 ` [PATCH v2 3/3] test/graph: fix graph autotest second run test failure kirankumark
2024-11-11 11:48 ` [PATCH v2 1/3] graph: avoid global node ID counter Robin Jarry
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=1731315747-7335-1-git-send-email-chcchc88@163.com \
--to=chcchc88@163.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=rjarry@redhat.com \
--cc=yanzhirun_163@163.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).