[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200401144109.GA29945@gardel-login>
Date: Wed, 1 Apr 2020 16:41:09 +0200
From: Lennart Poettering <mzxreary@...inter.de>
To: David Howells <dhowells@...hat.com>
Cc: Christian Brauner <christian.brauner@...ntu.com>,
torvalds@...ux-foundation.org, viro@...iv.linux.org.uk,
dray@...hat.com, kzak@...hat.com, mszeredi@...hat.com,
swhiteho@...hat.com, jlayton@...hat.com, raven@...maw.net,
andres@...razel.de, keyrings@...r.kernel.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
cyphar@...har.com
Subject: Re: Upcoming: Notifications, FS notifications and fsinfo()
On Di, 31.03.20 22:52, David Howells (dhowells@...hat.com) wrote:
> Christian Brauner <christian.brauner@...ntu.com> wrote:
>
> > querying all properties of a mount atomically all-at-once,
>
> I don't actually offer that, per se.
>
> Having an atomic all-at-once query for a single mount is actually quite a
> burden on the system. There's potentially a lot of state involved, much of
> which you don't necessarily need.
Hmm, do it like with statx() and specify a mask for the fields userspace
wants? Then it would be as lightweight as it possibly could be?
Lennart
--
Lennart Poettering, Berlin
Powered by blists - more mailing lists