From: Peter Zijlstra <peterz@infradead.org>
To: Kent Overstreet <kent.overstreet@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Dave Chinner <dchinner@redhat.com>,
darrick.wong@oracle.com, tytso@mit.edu,
linux-btrfs@vger.kernel.org, clm@fb.com, jbacik@fb.com,
viro@zeniv.linux.org.uk, willy@infradead.org
Subject: Re: [PATCH 04/10] locking: export osq_lock()/osq_unlock()
Date: Fri, 18 May 2018 11:52:04 +0200 [thread overview]
Message-ID: <20180518095204.GF12217@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180518074918.13816-9-kent.overstreet@gmail.com>
On Fri, May 18, 2018 at 03:49:06AM -0400, Kent Overstreet wrote:
No.. and most certainly not without a _very_ good reason.
next prev parent reply other threads:[~2018-05-18 9:52 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 7:48 [PATCH 00/10] RFC: assorted bcachefs patches Kent Overstreet
2018-05-18 7:49 ` [PATCH 01/10] mm: pagecache add lock Kent Overstreet
2018-05-18 13:13 ` Matthew Wilcox
2018-05-18 15:53 ` Christoph Hellwig
2018-05-18 17:45 ` Kent Overstreet
2018-05-23 23:55 ` Notes on locking for pagacache consistency (was: [PATCH 01/10] mm: pagecache add lock) Kent Overstreet
2018-05-20 22:45 ` [PATCH 01/10] mm: pagecache add lock Kent Overstreet
2018-05-23 15:22 ` Christoph Hellwig
2018-05-23 17:12 ` Kent Overstreet
2018-05-18 7:49 ` [PATCH 02/10] mm: export find_get_pages() Kent Overstreet
2018-05-18 16:00 ` Christoph Hellwig
2018-05-18 7:49 ` [PATCH 03/10] locking: bring back lglocks Kent Overstreet
2018-05-18 9:51 ` Peter Zijlstra
2018-05-18 10:13 ` Kent Overstreet
2018-05-18 11:03 ` Peter Zijlstra
2018-05-18 11:39 ` Kent Overstreet
2018-05-18 7:49 ` [PATCH 04/10] locking: export osq_lock()/osq_unlock() Kent Overstreet
2018-05-18 9:52 ` Peter Zijlstra [this message]
2018-05-18 10:18 ` Kent Overstreet
2018-05-18 11:08 ` Peter Zijlstra
2018-05-18 11:32 ` Kent Overstreet
2018-05-18 11:40 ` Peter Zijlstra
2018-05-18 12:40 ` Kent Overstreet
2018-05-18 7:49 ` [PATCH 05/10] don't use spin_lock_irqsave() unnecessarily Kent Overstreet
2018-05-18 16:01 ` Christoph Hellwig
2018-05-18 7:49 ` [PATCH 06/10] Generic radix trees Kent Overstreet
2018-05-18 16:02 ` Christoph Hellwig
2018-05-18 17:38 ` Kent Overstreet
2018-05-18 7:49 ` [PATCH 07/10] bcache: optimize continue_at_nobarrier() Kent Overstreet
2018-05-18 7:49 ` [PATCH 08/10] bcache: move closures to lib/ Kent Overstreet
2018-05-18 16:02 ` Christoph Hellwig
2018-05-18 7:49 ` [PATCH 09/10] closures: closure_wait_event() Kent Overstreet
2018-05-18 7:49 ` [PATCH 10/10] Dynamic fault injection Kent Overstreet
2018-05-18 16:02 ` Christoph Hellwig
2018-05-18 17:37 ` Kent Overstreet
2018-05-18 19:05 ` Andreas Dilger
2018-05-18 19:10 ` Kent Overstreet
2018-05-18 20:54 ` Andreas Dilger
2018-05-18 7:55 ` [PATCH 00/10] RFC: assorted bcachefs patches Kent Overstreet
2018-05-18 17:45 ` Josef Bacik
2018-05-18 17:49 ` Kent Overstreet
2018-05-18 18:03 ` Josef Bacik
2018-05-18 18:28 ` Kent Overstreet
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=20180518095204.GF12217@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=jbacik@fb.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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).