Re:Static IPs for Serverless Containers
by ec109685 on Monday December 02, 2024 @05:47PM
(#42301179)
If the nvidia driver has a bug, can one workload access data of another running on the physical machine?
E.g. it came up in this thread: https://news.ycombinator.com/item?id=41672168
Re:Static IPs for Serverless Containers
by JoshuaJB on Monday December 02, 2024 @06:37PM
(#42301572)
Yes. The kernel has access to data from every workload, and so technically a bug in _anything_ running at kernel level could result in data leakage.
Re:Static IPs for Serverless Containers
by doctorpangloss on Monday December 02, 2024 @05:45PM
(#42301168)
Suppose I ask for two H100s. Will I have GPU P2P capabilities?
Yep! This is something we have internal tests for haha, you have good instincts that it can be tricky. Here's an example of using that for multi-GPU training https://modal.com/docs/examples/llm-finetuning
Re:Static IPs for Serverless Containers
by doctorpangloss on Monday December 02, 2024 @06:27PM
(#42301492)
Okay, well think very deeply about what you are saying about isolation; the topology of the hardware; and why NVIDIA does not allow P2P access even in vGPU settings except in specific circumstances that are not yours. I think if it were as easy to make the isolation promises you are making, NVIDIA would already do it. Malformed NVLink messages make GPUs fall off the bus even in trusted applications.
Re:Static IPs for Serverless Containers
by thundergolfer on Monday December 02, 2024 @05:53PM
(#42301230)
Yes it will.
(I work at Modal.)
If you'd like to learn more, you can check out our docs here: https://modal.com/docs/guide/gpu
Re not using Kubernetes, we have our own custom container runtime in Rust with optimizations like lazy loading of content-addressed file systems. https://www.youtube.com/watch?v=SlkEW4C2kd4