Posts
197Following
422Followers
353
Toke Høiland-Jørgensen
toke
In which I explore the use of kprobes in the middle of a function and reveal that I am not, in fact, very good at reading assembly code... 😅
https://blog.tohojo.dk/2023/04/netfilter-packet-drop-attribution-using-bpf.html
1
2
6
Yeah, nice work, and thanks for the prodding 😊
0
0
1
Toke Høiland-Jørgensen
tokehttps://blog.tohojo.dk/2023/04/its-not-dead-its-resting.html
0
2
6
I know what you mean! Skipping plumbers myself this year for this reason. I think you could probably present remotely? 🤔
1
0
3
repeated
K. Ryabitsev-Prime 🍁
monsieuriconNow working on the other direction -- bugs added in bugzilla will be converted to mailing list threads and sent to proper maintainers (based on certain conditions, e.g. a "bugbot" flag needs to be set to "on" and the cf_subsystem custom field needs to match the corresponding MAINTAINERS entry). Should be done tomorrow, at which point I'll be looking for early testers. :)
1
6
12
Toke Høiland-Jørgensen
tokehttps://www.understandinglatency.com/recordings-2023
0
4
1
Who ever said cat herding was a waste of time? 😆 how else are we going to get all the proud roaming felines to pay attention to what's important? 😅
0
0
2
Toke Høiland-Jørgensen
tokehttps://www.understandinglatency.com/
The organisers were even kind enough to make me a fancy graphics to attach to this post! 😃
0
1
0
Toke Høiland-Jørgensen
tokeThis release includes three new utilities (xdp-bench, xdp-monitor and xdp-trafficgen) as well as frags support for libxdp and refcounting for XSK sockets!
Get it while it's hot off the press! 😃 #linux #XDP #BPF
https://github.com/xdp-project/xdp-tools/releases/tag/v1.3.0
0
0
0
Nah, but your general point is still valid - test with upstream, folks! 🙂
0
0
1
In this particular case I think that all Canonical did with their kernel was "have a working build environment", though... :/
(He's talking about the libxdp dispatcher, which works fine on upstream kernels. I know that because I wrote it 😅)
0
0
1
Toke Høiland-Jørgensen
tokehttps://lwn.net/SubscriberLink/921088/1946095baf6289a7/
0
11
9
repeated
Andi Popp 🇺🇦🎗️
AndiPopp@chaos.social
Because it has to be repeated again and again: We need to drastically reduce the number of cars to solve our problems.
0
1
0
repeated
repeated
@ljs @joel_linux RCU is simply broken down into three parts:
- grace periods
- quiescent states
- synchronization
A quiescent state is a time or action that guarantees all grace periods that were running at the time of the synchronization have finished (but you do not care about grace periods that started after synchronization).
If a link list protected by disabling preemption, then the grace period is when preemption is disabled, and the quiescent state is when all CPUs have scheduled. So you can remove an item from the link list (where all readers must have preemption disabled to read it), and then wait for all CPUs to schedule which guarantees nothing has access to the item, where you are now free to delete it without worrying that something is reading it.
That’s the simple case. There’s more complex cases, but it all comes down to the three parts above.
0
2
2