IRCaBot 2.1.0
GPLv3 © acetone, 2021-2022
#i2pd-dev
/2022/03/20
@Xeha
@orignal
Arch
Irc2PGuest27222
Irc2PGuest54664
Irc2PGuest59393
Irc2PGuest93848
Leopold
Meow
R4SAS
RN
RN_
StormyCloud
acetone
aeiou
aisle
ardu
aside
b3t4f4c3___
enoxa
eyedeekay
hk
phil
poriori
qend-irc2p
r00tobo
radakayot
rapidash
semantica
shiver_
u5657
woodwose
x74a6
yeti
R4SAS orignal: ping
R4SAS > number of descriptor also depends on number of timer. That means SSU and Streaming
det NTCP2 was what was taking the most descriptors. I don't really know about SSU I thought it was connectionless?
R4SAS SSU has timers
R4SAS and streams
R4SAS so every timer is file descriptor
det Ooh okay.
det Wait, a file descriptor for every timer? Really?
det1 I'd just... keep a linked list of timing events, in the... event loop.
det1 I don't know how boost does it.
orignal what?
orignal det Linux uses timerfd for each timer
orignal unfortunately SSU uses timer for each session
orignal going to be changed in SSU2
orignal your proposal is on the right tracks
orignal but if you decline NTCP2 connection it will use more SSU session that wouldn't solve a problem
orignal we know for sure that boost::deadline_time uses timerfd on linux