[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190806012027.GA6149@jagdpanzerIV>
Date: Tue, 6 Aug 2019 10:20:27 +0900
From: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
To: Al Viro <viro@...iv.linux.org.uk>
Cc: Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Chris Wilson <chris@...is-wilson.co.uk>,
David Howells <dhowells@...hat.com>,
Christoph Hellwig <hch@....de>,
David Airlie <airlied@...ux.ie>,
Daniel Vetter <daniel@...ll.ch>,
intel-gfx@...ts.freedesktop.org, dri-devel@...ts.freedesktop.org,
linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCHv2 2/3] i915: convert to new mount API
On (08/05/19 19:12), Al Viro wrote:
[..]
> On Tue, Aug 06, 2019 at 01:03:06AM +0900, Sergey Senozhatsky wrote:
> > tmpfs does not set ->remount_fs() anymore and its users need
> > to be converted to new mount API.
>
> Could you explain why the devil do you bother with remount at all?
I would redirect this question to i915 developers. As far as I know
i915 performance suffers with huge pages enabled.
> Why not pass the right options when mounting the damn thing?
vfs_kern_mount()? It still requires struct file_system_type, which
we need to get and put.
-ss
Powered by blists - more mailing lists