aesmd availability
Jarkko Sakkinen
maintainerI noticed that with aesmd the only feasible way to host it is to make a VM for it because:
- A beter predictable round-trip time for attestation.
- In the worst case, attestation could be potentially blocked.
Should the driver have a page locking mechanism to make this more robust, or do we want to satisfy to this? I'm not 100% sure what'd be the right path forward, just pointing out a potential availability issue.
BR, Jarkko
Jarkko Sakkinen
maintainerQuoted 9 lines · Jarkko Sakkinen
I noticed that with aesmd the only feasible way to host it is to make a VM for it because:
- A beter predictable round-trip time for attestation.
- In the worst case, attestation could be potentially blocked.Should the driver have a page locking mechanism to make this more robust, or do we want to satisfy to this? I'm not 100% sure what'd be the right path forward, just pointing out a potential availability issue.
Probably makes sense to spread just a bit :-)
BR, Jarkko
Hi Jarkko
Quoted 7 lines · Jarkko Sakkinen
Quoted 6 lines · Jarkko Sakkinen
I noticed that with aesmd the only feasible way to host it is to make a VM for it because:
- A beter predictable round-trip time for attestation.
- In the worst case, attestation could be potentially blocked.
I don't fully understand your description here. Based on what you said below, I think you are talking about how to improve (control of) EPC allocation for apps in case of over-subscription (i.e., when EPC runs out). My comments below are with this understanding.
In case you think there are limitations of aesmd implementation that prevent aesmd from being hosted in other than a separate VM, please create an issue on the corresponding GitHub.
Quoted 4 lines
Quoted 3 lines
Should the driver have a page locking mechanism to make this more robust, or do we want to satisfy to this? I'm not 100% sure what'd be the right path forward, just pointing out a potential availability issue.
Current swapping would ensure the last active pages be loaded so it gives some level of insurance that aesmd would be able to run as long as there is swapping RAM and other apps are not super active during attestation.
I think SGX cgroups support should help address this concern in a general way, which was discussed before and I think is in plan.
Not sure if lock works better, could you explain how it work?
Jarkko Sakkinen
maintainerQuoted 28 lines · Haitao Huang
Hi Jarkko
Quoted 7 lines · Jarkko Sakkinen
Quoted 6 lines · Jarkko Sakkinen
I noticed that with aesmd the only feasible way to host it is to make a VM for it because:
- A beter predictable round-trip time for attestation.
- In the worst case, attestation could be potentially blocked.I don't fully understand your description here. Based on what you said below, I think you are talking about how to improve (control of) EPC allocation for apps in case of over-subscription (i.e., when EPC runs out). My comments below are with this understanding.
In case you think there are limitations of aesmd implementation that prevent aesmd from being hosted in other than a separate VM, please create an issue on the corresponding GitHub.
Quoted 5 lines
Quoted 4 lines
Should the driver have a page locking mechanism to make this more robust,
or do we want to satisfy to this? I'm not 100% sure what'd be the right path forward, just pointing out a potential availability issue.
Quoted 8 lines
Current swapping would ensure the last active pages be loaded so it gives some level of insurance that aesmd would be able to run as long as there is swapping RAM and other apps are not super active during attestation.
I think SGX cgroups support should help address this concern in a general way, which was discussed before and I think is in plan.
Not sure if lock works better, could you explain how it work?
I agree that since cgroups is coming eventually it will address these concerns.
BR, Jarkko