[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cbbb6a1f-3203-9523-f47b-227fd646fd29@kernel.dk>
Date: Tue, 27 Jun 2017 07:26:55 -0600
From: Jens Axboe <axboe@...nel.dk>
To: Elena Reshetova <elena.reshetova@...el.com>
Cc: james.bottomley@...senpartnership.com,
linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
linux-scsi@...r.kernel.org, linux-btrfs@...r.kernel.org,
peterz@...radead.org, gregkh@...uxfoundation.org,
keescook@...omium.org, fujita.tomonori@....ntt.co.jp,
mingo@...hat.com, clm@...com, jbacik@...com, dsterba@...e.com
Subject: Re: [PATCH 0/5] v3 block subsystem refcounter conversions
On 06/27/2017 05:39 AM, Elena Reshetova wrote:
> Changes in v3:
> No changes in patches apart from trivial rebases, but now by
> default refcount_t = atomic_t and uses all atomic standard operations
> unless CONFIG_REFCOUNT_FULL is enabled. This is a compromize for the
> systems that are critical on performance and cannot accept even
> slight delay on the refcounter operations.
Is that true in 4.12-rc, or is that true in a later release once
Linus has pulled those changes in? If the latter, please resend
this when those changes are in, thanks.
--
Jens Axboe
Powered by blists - more mailing lists