NUMA Siloing in the FreeBSD Network Stack [pdf]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by loeg on Sunday September 22, 2019 @07:59PM (#21044838)

Not all of them are landed in CURRENT yet, much less stable/12. They'll be in 13.0; I can't speak to any future stable 12.2. On the other hand, CURRENT is pretty solid. A lot of folks, Netflix included, just run CURRENT.

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by yjftsjthsd-h on Monday September 23, 2019 @12:14AM (#21045868)

Wait, they run CURRENT in production? Is that... safe?

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by morning_gelato on Monday September 23, 2019 @01:26AM (#21046159)

There's at least one video online [1] that talks about Netflix's process for internal FreeBSD releases. They do 5 weeks of development and then 5 weeks of testing.

[1] https://www.youtube.com/watch?v=vcyQBup-Gto (about the 12 minute mark)

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by jlgaddis on Monday September 23, 2019 @01:13AM (#21046085)

In this particular (Netflix) case, what's the worst that could happen? One of their OCAs panics and falls over... and all customer traffic gets shifted to another OCA in the same or another location?

Sure, they might run into some bug in -CURRENT, but what's the chance of a bunch of their OCAs all hitting it at the same time?

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by branzo on Monday September 23, 2019 @03:00AM (#21046552)

I've been running CURRENT in production myself for about 2 years now. No problems so far.

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by 693471 on Tuesday September 24, 2019 @07:49AM (#21058940)

If you have kernel developers on your staff: yes

[ Parent | on HN ]

Re:NUMA Siloing in the FreeBSD Network Stack [pdf] by loeg on Monday September 23, 2019 @10:42AM (#21049334)

Yes.

[ Parent | on HN ]