* how to deduce connect/accept history from struct sock? (REPEAT)
@ 2004-05-13 22:30 Joey Dewille
0 siblings, 0 replies; only message in thread
From: Joey Dewille @ 2004-05-13 22:30 UTC (permalink / raw)
To: linux-kernel
Say a module is inserted that intercepts all socket operations and
it happened in the middle of several established connections.
Please answer what fields in struct sock or elsewhere can be examined
to determine reliably if the current established connections had been
accepted (i.e. accept call) or initiated (i.e. connect) from the local
machine.
--Joey
P.S. By the way, it seems to me that many fundamental structs in the
linux kernel such as sock, task_struct and others waste memory --
it would be preferable to pack some of their members in
bitfields. Everything and the kitchen sink can be found in those
structs which is wrong. Booleans are often given an entire char field.
Other members do not fall on natural alignment boundaries and create
holes. Memory is cheap but smaller memory footprint implies better
locality of reference, implies greater cache induced performance overall.
--
http://www.fastmail.fm - Consolidate POP email and Hotmail in one place
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2004-05-13 22:42 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-13 22:30 how to deduce connect/accept history from struct sock? (REPEAT) Joey Dewille
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox