Received: by 2002:a05:6a10:a0d1:0:0:0:0 with SMTP id j17csp482209pxa; Wed, 19 Aug 2020 06:55:58 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwkFwneh0hC53QU2nVaWKvrd83b0JyNFe6REQnETph2yDp8+0mveoO+2WaLIJhim04MNMhx X-Received: by 2002:a17:906:5ad8:: with SMTP id x24mr24159905ejs.329.1597845358299; Wed, 19 Aug 2020 06:55:58 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1597845358; cv=none; d=google.com; s=arc-20160816; b=I1ooGydoK7dRRscxH1g6P29HV7jl3Dbeei/UiHNeW0ZTGyEFDJ9yYms7g2PuELhl98 7rnndXYgNOsanWlRS7nZitOjiZalEN4r3YITlDvHXffSlwCeqlxmla5z2D1hi014dgkU IXyAq+RVUPlZuz8WwC5Pt+kQIjXQEoHM8SExuITyjyj10z5ks0Z7Rr30vx96FLcj+xjI y/9uem+5d49eUv2n1ctyM1lqGy/BFffmM7wVaZtj0YRy6ogwAdPcPiG6jQTM4WagXoJ1 LosgDp0VRAhMGD5UdIwdIUbn8jZ4BtQpB+FF84M342akZCJo/ae//0Ngw2PC08kNAslW yFNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=Xt/lOs3yw+tgIECaI15+mH2B0H4T/3Gk2EhK5NaldrU=; b=uIcQ9U9DXmjCUOiYbqXXBY0Fd7ct0cy35kY4laahmhHkl0d8Wewz4ETDwikc6Y79he RYaWX593ISdp90sVlTnN3KJ4NegHmAN6CpCqPWPqxOFeWcWjWtEh1Q7Z2Ty47E7I00Dc 0puTL6FPYubLh2vUmw+VYYOsJRS5Hq4zMu7Ow5RDAzusf6CqeTXfwlfWFOoo1ErGtBrT DIE3g1wdfjFQJ7TqzGcNV84IGasd/vVvrPv9havBzXg5UoExxTApbOM5aaE1VBmrZKyq kXM0KHC0PhM9q1JMWEzc0W03F8kMo2QHM+egcKjW4/Cjabo3PhiOiCPAnJT3qMuOkJMF K/cQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id f1si15859031edx.135.2020.08.19.06.55.34; Wed, 19 Aug 2020 06:55:58 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728516AbgHSNzE (ORCPT + 99 others); Wed, 19 Aug 2020 09:55:04 -0400 Received: from verein.lst.de ([213.95.11.211]:37889 "EHLO verein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726961AbgHSNzB (ORCPT ); Wed, 19 Aug 2020 09:55:01 -0400 Received: by verein.lst.de (Postfix, from userid 2407) id 8062B68BEB; Wed, 19 Aug 2020 15:54:55 +0200 (CEST) Date: Wed, 19 Aug 2020 15:54:55 +0200 From: Christoph Hellwig To: Tomasz Figa Cc: Christoph Hellwig , Mauro Carvalho Chehab , Thomas Bogendoerfer , "James E.J. Bottomley" , Joonyoung Shim , Seung-Woo Kim , Kyungmin Park , Ben Skeggs , Pawel Osciak , Marek Szyprowski , Matt Porter , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , Tom Lendacky , alsa-devel@alsa-project.org, linux-samsung-soc , linux-ia64@vger.kernel.org, linux-scsi@vger.kernel.org, linux-parisc@vger.kernel.org, Linux Doc Mailing List , nouveau@lists.freedesktop.org, Linux Kernel Mailing List , linux-nvme@lists.infradead.org, linux-mips@vger.kernel.org, linux-mm@kvack.org, netdev@vger.kernel.org, "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , Linux Media Mailing List Subject: Re: [PATCH 05/28] media/v4l2: remove V4L2-FLAG-MEMORY-NON-CONSISTENT Message-ID: <20200819135454.GA17098@lst.de> References: <20200819065555.1802761-1-hch@lst.de> <20200819065555.1802761-6-hch@lst.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 19, 2020 at 01:16:51PM +0200, Tomasz Figa wrote: > Hi Christoph, > > On Wed, Aug 19, 2020 at 8:56 AM Christoph Hellwig wrote: > > > > The V4L2-FLAG-MEMORY-NON-CONSISTENT flag is entirely unused, > > Could you explain what makes you think it's unused? It's a feature of > the UAPI generally supported by the videobuf2 framework and relied on > by Chromium OS to get any kind of reasonable performance when > accessing V4L2 buffers in the userspace. Because it doesn't do anything except on PARISC and non-coherent MIPS, so by definition it isn't used by any of these media drivers.