-
Notifications
You must be signed in to change notification settings - Fork 536
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
krings may not be properly aligned #921
Comments
You are right. tailroom is only used in VALE with a large enough alignment, but better to be explicit. I have pushed a new new commit for this. |
I actually encountered this when tailroom passed into the function is 0. We maintain a port of FreeBSD network stack to QNX. when we upgraded to GCC12 we started getting segfaults running ctrl-api-test due to an optimization using FP registers and simd instruction on unaligned kring address. For us the solution was to check that Your solution would not have fixed the problem for us. |
mmm, OK, that's an entirely different story. Those instructions want 16-byte alignment (old wisdom was that FP registers were off-limits in the kernel, but things change). I'll see what I can do. |
QNX is a micro kernel so we’re running in user space |
OK, second attempt. Incidentally, the misalignment may also have created false-sharing in multithreaded apps.
|
netmap/sys/dev/netmap/netmap.c
Line 877 in b58a473
Depending on the values of
[n]
(specifically ifn[0]
+n[1]
is odd), thenkring
may not be properly aligned.The text was updated successfully, but these errors were encountered: