From: "Huang\, Ying" <ying.huang@intel.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
<linux-kernel@vger.kernel.org>, <kernel-team@lge.com>,
<peterz@infradead.org>, <mingo@kernel.org>,
<jiangshanlai@gmail.com>, <josh@joshtriplett.org>,
<rostedt@goodmis.org>, <mathieu.desnoyers@efficios.com>,
<joel@joelfernandes.org>, <len.brown@intel.com>,
<glider@google.com>, <peter@hurleysoftware.com>, <aik@ozlabs.ru>
Subject: Re: [QUESTION] llist: Comment releasing 'must delete' restriction before traversing
Date: Wed, 01 Aug 2018 13:43:10 +0800 [thread overview]
Message-ID: <878t5qabgx.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20180731092950.GB12241@X58A-UD3R> (Byungchul Park's message of "Tue, 31 Jul 2018 18:29:50 +0900")
Byungchul Park <byungchul.park@lge.com> writes:
> I think rcu list also works well. But I decided to use llist because
> llist is simpler and has one less pointer.
>
> Just to be sure, let me explain my use case more:
>
> 1. Introduced a global list where single linked list is sufficient.
> 2. All operations I need is to add items and traverse the list.
> 3. Ensure the operations always happen within irq-disabled section.
> 4. I'm considering CONFIG_ARCH_HAVE_NMI_SAFE_CMPXCHG properly.
> 5. The list can be accessed by every CPU concurrently.
>
Can you provide more information about where is your use case? Is it a
kernel driver? Then it is better to submit the patch together with its
user.
And I have the similar concern as Steven Rostedt. That is, if you are
the only user forever, it's not necessary to change the common code.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2018-08-01 5:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-31 0:58 [QUESTION] llist: Comment releasing 'must delete' restriction before traversing Byungchul Park
2018-07-31 1:37 ` Huang, Ying
2018-07-31 5:25 ` Byungchul Park
2018-07-31 5:45 ` Huang, Ying
2018-07-31 4:30 ` Paul E. McKenney
2018-07-31 9:29 ` Byungchul Park
2018-07-31 14:30 ` Paul E. McKenney
2018-08-01 5:34 ` Byungchul Park
2018-08-01 5:43 ` Huang, Ying [this message]
2018-08-01 8:52 ` Byungchul Park
2018-07-31 8:52 ` Peter Zijlstra
2018-07-31 9:38 ` Byungchul Park
2018-07-31 13:46 ` Steven Rostedt
2018-08-01 5:35 ` Byungchul Park
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=878t5qabgx.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=aik@ozlabs.ru \
--cc=byungchul.park@lge.com \
--cc=glider@google.com \
--cc=jiangshanlai@gmail.com \
--cc=joel@joelfernandes.org \
--cc=josh@joshtriplett.org \
--cc=kernel-team@lge.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peter@hurleysoftware.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
/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