From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer
Date: Wed, 9 Dec 2020 12:14:57 +0100 [thread overview]
Message-ID: <X9CxsWOCoWPS8KZf@alley> (raw)
In-Reply-To: <20201209004453.17720-1-john.ogness@linutronix.de>
On Wed 2020-12-09 01:50:51, John Ogness wrote:
> Hello,
>
> Here is a v4 of the series to partially remove logbuf_lock.
> v3 is here[0]. This series removes logbuf_lock usage of most
> ringbuffer writers. The remaining logbuf_lock users are
> using the lock to synchronize other variables. These other
> users will be addressed in a later series.
>
> I have tried to keep these changes minimal so that we can feel
> comfortable for the upcoming 5.11 merge window.
Both patches are pushed in printk/linux.git, branch printk-rework.
I hurried so that we could get some testing linux-next before
the merge window opens.
We are going to see if the many barriers in the ring buffer
code are enough ;-) I keep my fingers crossed.
Best Regards,
Petr
prev parent reply other threads:[~2020-12-09 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 0:44 [PATCH next v4 0/2] printk: remove logbuf_lock writer-protection of ringbuffer John Ogness
2020-12-09 0:44 ` [PATCH next v4 1/2] printk: inline log_output(),log_store() in vprintk_store() John Ogness
2020-12-09 0:44 ` [PATCH next v4 2/2] printk: remove logbuf_lock writer-protection of ringbuffer John Ogness
2020-12-09 5:31 ` Sergey Senozhatsky
2020-12-09 11:11 ` Petr Mladek
2020-12-09 11:14 ` Petr Mladek [this message]
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=X9CxsWOCoWPS8KZf@alley \
--to=pmladek@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).