From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 3399CC4363D for ; Tue, 22 Sep 2020 16:42:47 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 87F63205CB for ; Tue, 22 Sep 2020 16:42:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=infradead.org header.i=@infradead.org header.b="m7mnIyy7" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 87F63205CB Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=infradead.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=owner-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix) id EDD6290001E; Tue, 22 Sep 2020 12:42:45 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id E8D54900003; Tue, 22 Sep 2020 12:42:45 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id D7CCC90001E; Tue, 22 Sep 2020 12:42:45 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0170.hostedemail.com [216.40.44.170]) by kanga.kvack.org (Postfix) with ESMTP id BE179900003 for ; Tue, 22 Sep 2020 12:42:45 -0400 (EDT) Received: from smtpin28.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 825F21EE6 for ; Tue, 22 Sep 2020 16:42:45 +0000 (UTC) X-FDA: 77291266290.28.cord99_2a076ff2714f Received: from filter.hostedemail.com (10.5.16.251.rfc1918.com [10.5.16.251]) by smtpin28.hostedemail.com (Postfix) with ESMTP id 5538B6C04 for ; Tue, 22 Sep 2020 16:42:45 +0000 (UTC) X-HE-Tag: cord99_2a076ff2714f X-Filterd-Recvd-Size: 4167 Received: from casper.infradead.org (casper.infradead.org [90.155.50.34]) by imf30.hostedemail.com (Postfix) with ESMTP for ; Tue, 22 Sep 2020 16:42:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=casper.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description; bh=Vlr5FEPRYDwFV5ct9yCcWf5tJnCkp0O4U+nuEZGp9d4=; b=m7mnIyy7qRuXOkvZYdRzuhCjLL 5CP0P5pePR+nA4qXJuGUuCMF4nabRXEq5u2TF6jhV5jVEgg0ehZykpXhmRWMwHZdSdvcjAv7iom0K PeV22OPv46gXU1rgFWGx2rGMQ6vOfB3Qx3eo+gXOKuJT4Agfi8/ZB1GsYjVlBaLiCsqjIaf2J2qDM F87PvcYOL+w25iSCY/HB7xqTlEI417SQIx6YUuvypsenY73zLxkyy98Y8QwM0pP+EZSmEYe1RD9aG ObWSHPwDQUnlxB5jUdG5u5BnSknBUGwY1eeRqq3/GoV8Efc5F/+VI42AnMf2jFLXzKVPf3EM7A3em VEMa452Q==; Received: from willy by casper.infradead.org with local (Exim 4.92.3 #3 (Red Hat Linux)) id 1kKlNI-0000ll-EO; Tue, 22 Sep 2020 16:42:40 +0000 Date: Tue, 22 Sep 2020 17:42:40 +0100 From: Matthew Wilcox To: Christoph Hellwig Cc: Andrew Morton , linux-mm@kvack.org, linux-kernel@vger.kernel.org, Uladzislau Rezki Subject: Re: [PATCH 2/2] vfree: Update documentation Message-ID: <20200922164240.GJ32101@casper.infradead.org> References: <20200921224628.20704-1-willy@infradead.org> <20200921224628.20704-2-willy@infradead.org> <20200922143506.GA26664@lst.de> <20200922150603.GH32101@casper.infradead.org> <20200922150910.GA29302@lst.de> <20200922152240.GI32101@casper.infradead.org> <20200922153136.GA30766@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200922153136.GA30766@lst.de> X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Sep 22, 2020 at 05:31:36PM +0200, Christoph Hellwig wrote: > On Tue, Sep 22, 2020 at 04:22:40PM +0100, Matthew Wilcox wrote: > > On Tue, Sep 22, 2020 at 05:09:10PM +0200, Christoph Hellwig wrote: > > > On Tue, Sep 22, 2020 at 04:06:03PM +0100, Matthew Wilcox wrote: > > > > I don't think it makes sense to list all vmalloc-style allocators here. > > > > It won't be updated by people who add new variations. How about this? > > > > > > > > * Free the virtually continuous memory area starting at @addr, as > > > > * obtained from one of the vmalloc() family of APIs. This will > > > > * usually also free the physical memory underlying the virtual > > > > * allocation, but that memory is reference counted, so it will not > > > > * be freed until the last user goes away. > > > > * > > > > * If @addr is NULL, no operation is performed. > > > > > > > > I'm trying to strike a balance between being accurate and not requiring > > > > device driver authors to learn all about struct page. I may be too > > > > close to the implementation to write good documentation for it. > > > > > > I think the above is sensible, but not enough. vmap really needs to > > > be treated special, as by default area->pages for vmap is NULL. So > > > for vfree to be useful on a vmap mapping, the callers needs to > > > manually set it up by poking into the internals. Actually, I think > > > we really want another API rather than vmap for that. Let me respin > > > my series to include that. > > > > I've been thinking about somethng like: > > > > void *vmap_mapping(struct address_space *mapping, pgoff_t start, > > unsigned long len); > > > > but it doesn't quite work for the shmem cases because they need to use > > shmem_read_mapping_page_gfp() instead of ->readpage. I'd also want it > > to work for DAX, but I don't have a user for that yet so it's hard to > > justify adding it. > > That seems a little too special cased to me. It's for filesystems that currently use map_bh or kmap_atomic() to get at their metadata (directories, superblocks, etc). > FYI, if you are fine with it I'll pick your two patches with the > updates from this thread up for my series. It has be now morphed into > a general vmalloc.c cleanup series. Yes, that's absolutely fine. Thanks!