[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/g/ - Technology

Name
Options
Comment
Verification
4chan Pass users can bypass this verification. [Learn More] [Login]
File
  • Please read the Rules and FAQ before posting.
  • You may highlight syntax and preserve whitespace by using [code] tags.

08/21/20New boards added: /vrpg/, /vmg/, /vst/ and /vm/
05/04/17New trial board added: /bant/ - International/Random
10/04/16New board for 4chan Pass users: /vip/ - Very Important Posts
[Hide] [Show All]


[Advertise on 4chan]


File: Tumblr_l_36441076739377.jpg (179 KB, 1170x818)
179 KB
179 KB JPG
previous: >>108485406

#define __NR_rt_sigqueueinfo    129
#define __NR_rt_tgsigqueueinfo 297

https://man7.org/linux/man-pages/man2/rt_sigqueueinfo.2.html

tl;dr:
primitives for io via signals

https://man7.org/linux/man-pages/man3/sigqueue.3.html
why the fuck would anyone ever use this? from what i can tell (and correct me if i am wrong), you can send - at best - a couple ints of data.... ???
literally why would you ever want this? i guess maybe if it's really high speed, it could be useful for certain operations? but like god.... i just can't fathom who's using this

relevant resources:
man man

man syscalls

https://man7.org/linux/man-pages/
https://linux.die.net/man/
https://elixir.bootlin.com/linux/
https://elixir.bootlin.com/musl/
https://elixir.bootlin.com/glibc/
>>
bampu
>>
holy dead thread... how depressing
>>
File: Tumblr_l_4318595099809.png (848 KB, 1600x1600)
848 KB
848 KB PNG
no one posted in my thread today
quite demoralizing
ok goodnight...
>>
>>108497349
to be fair from a quick glance this is a really useless syscall
>>
>>108497354
oh, it absolutely is. usually a couple of people will at least trash talk them for being so useless when it's this bad, though
>>
>>108497366
although maybe on account of the RT prefix these are meant to be used for like ultralight IPC in like RTOS situations or something?
what i was immediately reminded of was instructions that work with a really tiny globally atomic memory region amd gpus had for a while for global gpu thread synchronization and communication that AMD never really let anyone properly use and doesn't exist on newer hardware since they have real global thread sync instructions now
iirc it worked with their signalling (doorbells) infrastructure
>>
>>108497349
Sorry, I was busy all day today and didn't see the thread earlier.
>>
>>108497934
i'll forgive u just this once......
>>
>>108492651
how do you call syscalls right inside the kernel
>>
>>108497349
love u syscall anon
>>
>>108492651
>i guess maybe if it's really high speed, it could be useful for certain operations?
I actually doubt sending signals is faster than other types of IPC, since as you noted, nobody uses them for high speed communication, so they never got optimized for that
>you can send - at best - a couple ints of data.... ??? literally why would you ever want this?
I suspect this was added before we got proper message queues. An int is still more than enough to send an internal opcode
>>
sucking syscall anon's cock with my butthole
>>
>>108499459
there's a syscall instruction and they should be at fixed memory addresses for a given kernel version
and on windows, since it has a proper stable kernel ABI parts of its kernel interface are exported from its binaries, iirc both ntoskrnl.exe and ntdll.dll export the main subset but random shared libraries export other parts of the NT API, you can tell because NT API functions are formatted slightly differently to Win32 API functions (SubsystemFunctionName vs FunctionName)



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.