Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Mon, 27 Mar 2023 14:37:01 -0400
From:   Kent Overstreet <kent.overstreet@linux.dev>
To:     Matthew Wilcox <willy@infradead.org>
Cc:     "Fabio M. De Francesco" <fmdefrancesco@gmail.com>,
        Alexander Viro <viro@zeniv.linux.org.uk>,
        Benjamin LaHaise <bcrl@kvack.org>,
        linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
        linux-kernel@vger.kernel.org,
        "Venkataramanan, Anirudh" <anirudh.venkataramanan@intel.com>,
        Ira Weiny <ira.weiny@intel.com>, Jeff Moyer <jmoyer@redhat.com>
Subject: Re: [PATCH v3] fs/aio: Replace kmap{,_atomic}() with
 kmap_local_page()
Message-ID: <ZCHiTYyzBzHFa9xX@moria.home.lan>
References: <20230119162055.20944-1-fmdefrancesco@gmail.com>
 <2114426.VsPgYW4pTa@suse>
 <ZCGYps2z5IlaEaxU@casper.infradead.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ZCGYps2z5IlaEaxU@casper.infradead.org>
Precedence: bulk

On Mon, Mar 27, 2023 at 02:22:46PM +0100, Matthew Wilcox wrote:
> Or should we just stop allocating aio rings from HIGHMEM and remove
> the calls to kmap()?  How much memory are we talking about here?

I don't think that should stop us from taking these patches, but yes.