News for hackers. Stuff that matters.

A comment on Intel's make-or-break 18A process node debuts for data center with 288-core Xeon. Parent comment

Re:Intel's make-or-break 18A process node debuts for data ce... by fc417fc802 on Tuesday March 03, 2026 @06:34PM (#47240696)
Do the partitioned stacks of network namespaces share a single underlying global stack or are they fully independent instances? (And if not, could they be made so?)
[ Parent | on HN ]
Re:Intel's make-or-break 18A process node debuts for data ce... by wmf on Tuesday March 03, 2026 @06:58PM (#47240975)
Usually network namespaces are linked together with a single bridge so you can get lock contention there.

If you have a separate physical NIC for each namespace you probably won't have any contention.

[ Parent | on HN ]
Re:Intel's make-or-break 18A process node debuts for data ce... by jeffbee on Tuesday March 03, 2026 @07:19PM (#47241191)
I think you could get much of the way there by isolating a single NIC's receive queues, so the kernel doesn't decide to run off and service softirqs for random foreign tasks just because your task called tcp_sendmsg.
[ Parent | on HN ]