🐝New Cilium Contributor🐝
The newest Cilium contributor is Oleh Neichev
They helped add a containerSelector that allows filtering policies by container name in Tetragon
https://t.co/o8Rlm7hh2N
Tetragon 1.0 has landed! 🎉 It features new default observability policies, extensive overhead benchmarks, and a ton of maturization, along with many additional features. Let's take a closer look 🧵
https://t.co/8VWjyn0AkZ
🚀 Tetragon 1.0 - Default observability policies, overhead benchmarks, kubectl exec monitoring, and much more! Read more in the blog: https://t.co/4hTYmsQXf4
We are happy to host our alumni Dr. Kornilios Kourtis (@kkourt) for a talk on his current work! If you are interested to see how to support innovation in Operating Systems with #eBPF, join us on Thursday, 22/12, 10:45am at the Amphitheater of the central library of NTUA.
@SciHardware @ProjectPhysX @IanCutress That was not our experience. Optane SSDs did offer significant lower latency: https://t.co/aO3GGBisqk. Did not fully read the paper, but my guess is that the problem lies in the software stack, not the device.
Congratulations to all of you who got a paper accepted to #Eurosys. Reminder to submit your papers to the Artefact Evaluation https://t.co/qfDZMwrucR. Help the community encourage reproducible research and get your hard work officially recognised.
I will be talking about measuring network performance on Kubernetes: https://t.co/HTuq66bj21. (note that link of tweet below points to a different awesome talk by @GhagAditi and @martyns).
We are thrilled to announce that Cilium has been accepted as a mentor organization in this year's Google Summer of Code! 🎉 #GSoC2021
For more details see:
https://t.co/xal1jaQ9HL
Or join #gsoc on https://t.co/B1ret1563Y
We are looking for motivated students, post-docs and researchers to join the SuperComputing'21 Artifact Description/Evaluation Committee. We especially encourage members from underrepresented groups to apply. Self-nominate here: https://t.co/jGGZrDKw1w
cc @Supercomputing
@smdiehl Under this model, pointers to struct elements should fall into the latter category since you can do pointer arithmetic (e.g., offsetof) on them. Hence, Not sure how useful such a static distinction would be. I think a "I know-what-I'm-doing" mode (e.g., Rust's unsafe) is better.