Hi everybody,
I was looking through the code for the TCP implementation in kernel
2.0.34. Just had a doubt, on call to accept(), when a new sock structure
is established, does it have the same options as were set for the old one
using setsockopt(). It doesn't look so to me in the code...or am I
woefully off the mark?
Also, is the following execution path the way to go for user level
accept()?
accept()->sys_accept()->inet_dup()->inet_create()
after which the regular tcp_accept() gets called?
Thanks
Hari
------------------------------------------------------------------------------
Hariharan L. Thantry
thantryh@cse.msu.edu
4642, S. Hagadorn Road, #E6 Dept of Computer Science and Engg
East Lansing, MI 48823 Michigan State University
East Lansing, MI 48824-1226
Ph(res): 1-517-332-2645 Ph(off): 1-517-353-6646
-----------------------------------------------------------------------------
---------- Forwarded message ----------
Date: Tue, 1 Aug 2000 23:10:37 -0400 (EDT)
From: Hariharan L Thantry <thantryh@cse.msu.edu>
Subject: Domains, families and TCP
Hi everybody,
I was wondering if anybody could tell me where the initialisation code for
the different address families (AF_UNIX, AF_INET etc) lay. Also where is
the structure definition for these address families? I found that for the
AF_INET family, there is a structure named struct inet_protocol{} in
protocol.h, and initialised in protocol.c, but what about the other
families? I recollect reading somewhere about some pops vector, but I
dunno.
Also, where is the snmp variable defined in struct
tcp_mib{unsinged long tcpoutsegs;} updated?
Have a great day.
Regards
Hari
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.rutgers.edu
