From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f69.google.com (mail-pl0-f69.google.com [209.85.160.69]) by kanga.kvack.org (Postfix) with ESMTP id 672696B06D2 for ; Fri, 11 May 2018 17:13:42 -0400 (EDT) Received: by mail-pl0-f69.google.com with SMTP id i1-v6so3902664pld.11 for ; Fri, 11 May 2018 14:13:42 -0700 (PDT) Received: from mail-sor-f65.google.com (mail-sor-f65.google.com. [209.85.220.65]) by mx.google.com with SMTPS id t30-v6sor1204047pgo.37.2018.05.11.14.13.41 for (Google Transport Security); Fri, 11 May 2018 14:13:41 -0700 (PDT) Subject: Re: [PATCH 00/10] Misc block layer patches for bcachefs References: <20180509013358.16399-1-kent.overstreet@gmail.com> From: Jens Axboe Message-ID: Date: Fri, 11 May 2018 15:13:38 -0600 MIME-Version: 1.0 In-Reply-To: <20180509013358.16399-1-kent.overstreet@gmail.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: Kent Overstreet , linux-kernel@vger.kernel.org, linux-block@vger.kernel.org, linux-mm@kvack.org, Ingo Molnar On 5/8/18 7:33 PM, Kent Overstreet wrote: > - Add separately allowed mempools, biosets: bcachefs uses both all over the > place > > - Bit of utility code - bio_copy_data_iter(), zero_fill_bio_iter() > > - bio_list_copy_data(), the bi_next check - defensiveness because of a bug I > had fun chasing down at one point > > - add some exports, because bcachefs does dio its own way > - show whether fua is supported in sysfs, because I don't know of anything that > exports whether the _block layer_ specifically thinks fua is supported. Looked over the series, and looks like both good cleanups and optimizations. If we can get the mempool patch sorted, I can apply this for 4.18. -- Jens Axboe