Ayush Ranjan

> we have no way of generating unique inode numbers for synthetic files in the same gofer mount. Surely we can address this by using a different device ID for...

Your understanding of the two approaches is correct. > Approach B, relying on the host's overlayfs, makes runsc as a whole somewhat more subject to any potential quirks of the...

I recently implemented @nixprime's suggestion from above (use remote inode numbers directly & map remote device IDs) on my local machine and didn't see much performance gains on broader filesystem...

@crappycrypto I am curious to know if slow directory operations for large directories is still an issue for you.

runsc does not implement the `update` command. We should add support for it, but probably won't have cycles. Happy to get OSS contributions for this! References: runc man page: https://github.com/opencontainers/runc/blob/main/man/runc-update.8.md...

I would start by looking through https://cs.opensource.google/gvisor/gvisor/+/master:runsc/cmd/ directory. All runsc commands are implemented there. Then see the [runc implementation](https://github.com/opencontainers/runc/blob/main/update.go) to understand what the `update` command does and implement the same...

> wanted to get some high level feedback first on the implementation before I proceed, to make sure I'm on the right track I think you are on the right...

I left some comments in #9369. I am curious what is the higher level goal of this change? Is this a starter task of some sort?

Note that the test will not run unless you modify the BUILD file to add the test to `linux_test`.

Let me know if https://github.com/google/gvisor/pull/9828 solves this issue. Do you know if this will repro on T4 as well? Hard to get a hold of A100. But I will try...