Tweetovi

Blokirali ste korisnika/cu @cirowrc

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @cirowrc

  1. proslijedio/la je Tweet
    8. sij

    Excited to what people do with the set_pipeline step! 🛠️

    Poništi
  2. proslijedio/la je Tweet
    19. stu 2019.

    security team put together a blog that shows the security and design principles behind gVisor! Should be a fun read for those who care about container security.

    Poništi
  3. proslijedio/la je Tweet
    Poništi
  4. proslijedio/la je Tweet
    16. lis 2019.

    Defer gets cheaper, but panic/recover is more expensive. Cost of defer: 34ns -> 6ns. Cost of panic/recover: 62ns -> 255ns

    Poništi
  5. proslijedio/la je Tweet
    28. ruj 2019.
    Prikaži ovu nit
    Poništi
  6. proslijedio/la je Tweet
    17. srp 2019.

    We've got a new blog, and we're kicking it off with a long-awaited roadmap update!

    Poništi
  7. proslijedio/la je Tweet
    15. srp 2019.

    Announcing my next book: BPF Performance Tools: Linux System and Application Observability, for which I developed over 100 new tools

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    12. srp 2019.

    Did you ever ask yourself if cgroups (containers, pods, whathaveyou) can impact the runtime? I did and here's what I learned... (thread) 👇

    Prikaži ovu nit
    Poništi
  9. proslijedio/la je Tweet

    One thing that seems to have gotten hidden from the GitHub announcements is actually THE MOST VALUABLE feature for open source maintainers: The ability to have private discussions and code review about security vulnerabilities WITHIN your repo.

    Prikaži ovu nit
    Poništi
  10. 16. svi 2019.
    Poništi
  11. 11. svi 2019.

    naturally, not on localhost - that's two pods communicating through a service on GKE with receiver & transmitter sitting on different nodes

    Prikaži ovu nit
    Poništi
  12. 11. svi 2019.

    the details: - single connection - just `splice`ing from the receiving socket directly to a fd pointing to `/dev/null`

    Prikaži ovu nit
    Poništi
  13. 11. svi 2019.

    it's just so crazy how "stressing" a linux node by making it receive at consistent 10Gbps reveals that just ~15% of sys time and ~14% of softirq time is needed (of a single core) 🤯

    Prikaži ovu nit
    Poništi
  14. 27. tra 2019.

    The cool thing is that once that's done, iterating on it becomes quite simple once you have images built in a multi-platform manner 👍

    Prikaži ovu nit
    Poništi
  15. 27. tra 2019.

    You also need to rebuild Concourse itself (which now is a single binary coming from a single repo) - we don't ship armv7 builds yet. With concourse + dependencies + resources types all built from scratch, you're good to go! Quite timely with Docker partnering with ARM

    Prikaži ovu nit
    Poništi
  16. 27. tra 2019.

    Here's what it takes to get it bootstrapped: - modify gdn to include fix for idmapper to work on 32bit + disable seccomp (for now), - rebuild gdn + its dependencies (runc, dadoo, gdn-init ...) - make the `registry-image` platform-aware (so it finds ARM container image refs)

    Prikaži ovu nit
    Poništi
  17. 27. tra 2019.

    yaaay 🙌! I just got workers running with almost full containerization on a Raspberry PI! (had to disable seccomp - which is arch-specific -, but it's almost there!) More on ARM it soon

    Prikaži ovu nit
    Poništi
  18. proslijedio/la je Tweet
    28. ožu 2019.

    Finally! Great step forward by the community. The hype to reward ratio of tracing is skewed in the wrong direction, and competing projects/standards were not helping. Let's help folks get the data out so we can focus on better viz/analysis. Yay! 🎉

    Poništi
  19. proslijedio/la je Tweet
    27. ožu 2019.

    This is how an exciting commit description starts: > This work adds a NAT engine in BPF which is working together with > Cilium's BPF-based connection tracker. [...] One of the final steps to a kube-proxy free k8s environment.

    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    6. ožu 2019.

    At long last, v5.0 is out! Release notes: - there are literally too many big things to fit here. Thanks so much to all who took part in this. Looking forward releasing much more frequently from here on!

    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·