On 11/14/22 8:35 PM, Miklos Szeredi wrote:
On Mon, 14 Nov 2022 at 10:00, Abel Wu <wuyun.abel@xxxxxxxxxxxxx> wrote:
Hi Miklos and anyone interested in this proposal, is there any update on
this? Sorry that I didn't find any..
No update.
Which part are you interested in?
We noticed that atop(1) can introduce a burst cpu usage once number of
processes becoming large. It is mostly due to the overhead of massive
syscalls. There are similar cases like monitor agents recording system
status and consuming resources in modern data centers. So it would be
nice to get a bunch of info in one syscall.
Getting mount attributes? Or a generic key-value retrieval and
storage interface?
The latter.
For the first one there are multiple proposals, one of them is adding
a new system call using binary structs. The fsinfo(2) syscall was
deemed overdesigned and rejected. Something simpler would probably be
fairly uncontroversial.
As for the other proposal it seems like some people would prefer a set
of new syscalls, while some others would like to reuse the xattr
syscalls. No agreement seems to have been reached.
So the divergence comes from 'how' rather than 'why', right?
Thanks & Best,
Abel
Also I think a notification system for mount related events is also a
much needed component. I've tried to explore using the fsnotify
framework for this, but the code is pretty convoluted and I couldn't
get prototype working.
Thanks,
Miklos
