Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-18 Thread Andi Kleen
David Miller [EMAIL PROTECTED] writes: This is limiting embryonic mini-socket creation. The listen overflow should only increment when the 3-way handshake completion is aborted because the listening socket limit is exceeded, which is entirely different from the embryonic limit. That's true,

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-18 Thread Rick Jones
Andi Kleen wrote: David Miller [EMAIL PROTECTED] writes: This is limiting embryonic mini-socket creation. The listen overflow should only increment when the 3-way handshake completion is aborted because the listening socket limit is exceeded, which is entirely different from the embryonic

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-17 Thread David Miller
I'm rebasing a 500 patch tree which has tons of merge conflicts today, so I lack the time to answer your question. Suffice it to say you could do a little bit of legwork to figure out the answer by researching inet_csk_reqsk_queue_is_full() and determining what sets the state tested by that

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-17 Thread Rick Jones
David Miller wrote: From: Rick Jones [EMAIL PROTECTED] Date: Mon, 10 Sep 2007 11:42:18 -0700 I've been digging around to see about inducing /proc/net/tcp to show some interesting things for listen sockets (eg backlog depth, its max, and dropped connection requests). While there I've noticed

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-14 Thread David Miller
From: Rick Jones [EMAIL PROTECTED] Date: Mon, 10 Sep 2007 11:42:18 -0700 I've been digging around to see about inducing /proc/net/tcp to show some interesting things for listen sockets (eg backlog depth, its max, and dropped connection requests). While there I've noticed that both

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-14 Thread David Miller
From: Sridhar Samudrala [EMAIL PROTECTED] Date: Mon, 10 Sep 2007 14:54:43 -0700 looks like it is a hole in the stats. I think we should increment LISTENOVERFLOWS or LISTENDROPS in tcp_v[46]_conn_request too if the SYN is dropped. No we should not. This is limiting embryonic mini-socket

why does tcp_v[46]_conn_request not inc MIB stats

2007-09-10 Thread Rick Jones
I've been digging around to see about inducing /proc/net/tcp to show some interesting things for listen sockets (eg backlog depth, its max, and dropped connection requests). While there I've noticed that both tcp_v[46]_syn_recv_sock and tcp_v[46]conn_request both check that the listen queue

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-10 Thread Sridhar Samudrala
On Mon, 2007-09-10 at 11:42 -0700, Rick Jones wrote: I've been digging around to see about inducing /proc/net/tcp to show some interesting things for listen sockets (eg backlog depth, its max, and dropped connection requests). backlog depth(acceptq length) for a listening socket should be

Re: why does tcp_v[46]_conn_request not inc MIB stats

2007-09-10 Thread Rick Jones
Sridhar Samudrala wrote: On Mon, 2007-09-10 at 11:42 -0700, Rick Jones wrote: I've been digging around to see about inducing /proc/net/tcp to show some interesting things for listen sockets (eg backlog depth, its max, and dropped connection requests). backlog depth(acceptq length) for a