All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Huang\, Ying" <ying.huang@intel.com>
To: Byungchul Park <byungchul.park@lge.com>
Cc: <linux-kernel@vger.kernel.org>, <kernel-team@lge.com>,
	<peterz@infradead.org>, <mingo@kernel.org>,
	<jiangshanlai@gmail.com>, <paulmck@linux.vnet.ibm.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: Tue, 31 Jul 2018 09:37:50 +0800	[thread overview]
Message-ID: <87d0v4mbgx.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <1532998716-5037-1-git-send-email-byungchul.park@lge.com> (Byungchul Park's message of "Tue, 31 Jul 2018 09:58:36 +0900")

Byungchul Park <byungchul.park@lge.com> writes:

> Hello folks,
>
> I'm careful in saying.. and curious about..
>
> In restrictive cases like only addtions happen but never deletion, can't
> we safely traverse a llist? I believe llist can be more useful if we can
> release the restriction. Can't we?
>
> If yes, we may add another function traversing starting from a head. Or
> just use existing funtion with head->first.
>
> Thank a lot for your answers in advance :)

What's the use case?  I don't know how it is useful that items are never
deleted from the llist.

Some other locks could be used to provide mutual exclusive between

- llist add, llist traverse

and

- llist delete

Is this your use case?

Best Regards,
Huang, Ying

  reply	other threads:[~2018-07-31  1:37 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 [this message]
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
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=87d0v4mbgx.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 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.