Dmitrii Kuvaiskii

@vasanth-intel So PR #1513 doesn't help, right? The performance overhead is still huge?

This issue is almost 1 year old. @vasanth-intel If this is still reproduced on latest Gramine, and we need to think about fixing it, please reopen the issue and add...

> Also, SIGSTRUCT depends on the exact manifest contents (it hashes it), which sounds bad for this design: we'd need to split the file somehow and be very strict and...

Jenkins, test this please

@vasanth-intel Sorry, could you put the results in tables where we compare three things: 1. Native performance 2. Performance with Gramine `master` (EDMM but without perf optimization of this PR)...

The LFX Insights tool looks pretty interesting; I took a look at the example of https://insights.lfx.linuxfoundation.org/foundation/ccc/overview/github?project=coconut-svsm. However, I am also strongly against making you an admin. Why can't we add...

> The metrics team stated, "currently we cannot support a maintainer being able to onboard their project themselves in CM ... however, I'd be open to exploring how that could...

### Update from May 2024 I was looking at the possibility of removing `libos_handle::dentry` field. Unfortunately, this is still far away from being possible. There are two Gramine problems that...

Closing this as it is a duplicate of #21

I'm not sure how this is possible, because the limit of possible PIDs is ~4 million: https://github.com/gramineproject/gramine/blob/1cf1f46646646a3b9c6b371e67c80e945577456a/libos/include/libos_types.h#L30-L31 Apparently this sub-test of `stress-ng` allocate a crazy amount of processes, each with...