From: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
To: Petr Mladek <pmladek@suse.com>
Cc: Byungchul Park <byungchul.park@lge.com>,
Steven Rostedt <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Cong Wang <xiyou.wangcong@gmail.com>,
Dave Hansen <dave.hansen@intel.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Mel Gorman <mgorman@suse.de>, Michal Hocko <mhocko@kernel.org>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Vlastimil Babka <vbabka@suse.cz>,
Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Jan Kara <jack@suse.cz>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
rostedt@home.goodmis.org, kernel-team@lge.com
Subject: Re: [PATCH v4] printk: Add console owner and waiter logic to load balance console writes
Date: Tue, 12 Dec 2017 14:39:21 +0900 [thread overview]
Message-ID: <20171212053921.GA1392@jagdpanzerIV> (raw)
In-Reply-To: <20171208140022.uln4t5e5drrhnvvt@pathway.suse.cz>
Hello,
On (12/08/17 15:00), Petr Mladek wrote:
[..]
> > However, now that cross-release was introduces, lockdep can be applied
> > to semaphore operations. Actually, I have a plan to do that. I think it
> > would be better to make semaphore tracked with lockdep and remove all
> > these manual acquire() and release() here. What do you think about it?
>
> IMHO, it would be great to add lockdep annotations into semaphore
> operations.
certain types of locks have no guaranteed lock-unlock ordering.
e.g. readers-writer locks, semaphores, etc.
for readers-writer lock we can easily have
CPU0 CPU1 CPU2 CPU3 CPU4
read_lock
write_lock
// sleep because
// of CPU0
read_lock
read_unlock read_lock
read_unlock read_lock
read_unlock
read_unlock
// wake up CPU1
so for CPU1 the lock was "locked" by CPU0 and "unlocked" by CPU4.
semaphore not necessarily has the mutual-exclusion property, because
its ->count is not required to be set to 1. in printk we use semaphore
with ->count == 1, but that's just an accident.
-ss
p.s.
frankly, I don't see any "locking issues" in Steven's patch.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-12 5:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-08 15:27 [PATCH v4] printk: Add console owner and waiter logic to load balance console writes Steven Rostedt
2017-11-09 10:12 ` Michal Hocko
2017-11-09 10:22 ` [PATCH v4] printk: Add console owner and waiter logic to loadbalance " Tetsuo Handa
2017-11-09 10:26 ` Michal Hocko
2017-11-09 11:03 ` Tetsuo Handa
2017-11-09 11:31 ` Michal Hocko
2017-11-09 12:07 ` Tetsuo Handa
2017-11-24 15:54 ` [PATCH v4] printk: Add console owner and waiter logic to load balance " Petr Mladek
2017-11-24 15:58 ` Petr Mladek
2017-11-27 8:53 ` Byungchul Park
2017-11-28 1:42 ` Byungchul Park
2017-12-08 14:00 ` Petr Mladek
2017-12-12 5:39 ` Sergey Senozhatsky [this message]
2017-12-12 19:27 ` Steven Rostedt
2017-12-13 1:50 ` Sergey Senozhatsky
2017-12-14 14:34 ` Petr Mladek
2017-12-14 13:51 ` Petr Mladek
2017-11-27 8:48 ` Byungchul Park
2017-11-28 6:23 ` Sergey Senozhatsky
2017-12-22 10:31 ` Petr Mladek
2017-12-22 12:44 ` Steven Rostedt
2018-01-10 12:50 ` Petr Mladek
-- strict thread matches above, loose matches on Subject: below --
2017-11-08 15:13 Steven Rostedt
2017-11-08 15:03 Steven Rostedt
2017-11-08 15:10 ` Steven Rostedt
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=20171212053921.GA1392@jagdpanzerIV \
--to=sergey.senozhatsky.work@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=byungchul.park@lge.com \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mhocko@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=rostedt@home.goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=xiyou.wangcong@gmail.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).