Hacker Newsnew | past | comments | ask | show | jobs | submit | haberman's favoriteslogin

This is getting a little long in the tooth but I created a few videos and did some tests around cgroups back in 2013-2014. Both these help explain the underpinnings of Docker and I guess Kubernetes now too. Turtles all the way up. I'm just mentioning this since these are still some of my most popular videos and still the core tech under the hood.

A personal note here too. cgroups were invented at Google in the early 2000's. If you're using search today, gmail, docs, maps, etc. You're using cgroups. It sounds simple but this tech really powered a whole wave of innovation/startups/projects that almost everyone interacts with on a daily basis. Either through touching a Google service or interacting with anyone using Docker or Kubernetes (running on cgroups/namespaces). Pretty impressive.

#14 - Introduction to Linux Control Groups (Cgroups)

https://sysadmincasts.com/episodes/14-introduction-to-linux-...

#24 - Introduction to Containers on Linux using LXC

https://sysadmincasts.com/episodes/24-introduction-to-contai...


Agendas are like you-know-whats... everyone's got one.

I wouldn't say I agree with them on everything but this is definitely on the sane side as agendas go, especially these days when vast numbers of people seem to have eaten the brown acid. They also deserve a bit of credit for being pretty up front with it.


Out of curiosity, where would one find an explanation (potentially dry, long, and complicated) of the algos you mention here?

In other words - how did you get to know them?


> What kind of "stream" did you have in mind?

The same kind the author means. I didn't coin this term or introduce it to the discussion.

> For the OS to do software mixing, it is basically going to run a "for" loop over the audio buffers and add them up to produce the audio buffer that goes to the hardware. When is it going to run that loop?

Right, the author is saying that the OS is already doing this, and additionally the application does the same thing before sending a combined stream to the OS. So to answer your question of "when is [the OS] going to run that loop?" My answer is the same time it does now. I'm not proposing any changes to how the OS works.

My question is: why does the application need to do that work? Why can't it send each stream to the OS to have them be combined in only one place?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: