Hello,
It seems like linux replaces sock with tcp_tw_bucket structure in the
sock list in order to "work around the memory consumption problems for
the heavilly loaded server".
The header file tcp.h has some comments before declaring
"tcp_tw_bucket" structure. It is done in tcp_input.c.
But a
I found this condition only happens when the sock state is TCP_TIME_WAIT.
I don't know if this helps.
Sourav Ghosh wrote:
> Hello,
>
> I'm using linux 2.2.15 kernel on redhat.
> I have added some variables (pointers) on "sock" data structure.
> I was initializing them to NULL in sk_alloc() func
Jacob L E Blain Christen wrote:
> looking further at
> net/ipv4/tcp_ipv4.c:tcp_create_openreq_child() (for 2.2.16)
> and
> net/ipv4/tcp_minisocks.c:tcp_create_openreq_child() (for 2.4.x)
>
> immediately after the sk_alloc() call (if it successful) it calls
> memcpy(newsk, sk, sizeof(*news
looking further at
net/ipv4/tcp_ipv4.c:tcp_create_openreq_child() (for 2.2.16)
and
net/ipv4/tcp_minisocks.c:tcp_create_openreq_child() (for 2.4.x)
immediately after the sk_alloc() call (if it successful) it calls
memcpy(newsk, sk, sizeof(*newsk))
i suggest setting your NULL initial value
im a kernel newbie here so pardon "the blind leading the blind" ...
doing a quick search for all calls to sk_alloc in the entire kernel
sources
yields only one call that sets the "zero out the allocated struct"
boolean
to false and that is:
net/ipv4/tcp_minisocks.c:tcp_create_openreq_chil
Hello,
I'm using linux 2.2.15 kernel on redhat.
I have added some variables (pointers) on "sock" data structure.
I was initializing them to NULL in sk_alloc() function.
But it seems some sock structures are allocated for TCP bypassing this
sk_alloc() and due to this my added pointers are not ini
6 matches
Mail list logo
