| To: | "Nivedita Singhvi" <niv@xxxxxxxxxx> |
|---|---|
| Subject: | Re: question about linux tcp request queue handling |
| From: | "Paul Albrecht" <palbrecht@xxxxxxxxx> |
| Date: | Mon, 7 Jul 2003 16:30:47 -0700 |
| Cc: | linux-kernel@xxxxxxxxxxxxxxx, "netdev" <netdev@xxxxxxxxxxx> |
| References: | <3F08858E.8000907@us.ibm.com> <001a01c3441c$6fe111a0$6801a8c0@oemcomputer> <3F08B7E2.7040208@us.ibm.com> <000d01c3444f$e6439600$6801a8c0@oemcomputer> <3F090A4F.10004@us.ibm.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Nivedita Singhvi writes: > > Again, youre limiting the number of connnection requests > that are allowed to wait in the *accept* queue, where > we move to once we're ESTABLISHED. You arent limiting > a request sitting in the SYN queue. > This statement is inconsistent with the description of this scenario in Steven's TCP/IP Illustrated. Specifically, continuing the handshake in the TCP layer, i.e., sending a syn/ack and moving to the syn_recd state, is incorrect if the limit of the server's socket backlog would be exceeded. How do you account for this discrepancy between linux and other berkeley-derived implementations? |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: disablenetwork() syscall?, Mitchell Blank Jr |
|---|---|
| Next by Date: | Re: question about linux tcp request queue handling, Andi Kleen |
| Previous by Thread: | Re: question about linux tcp request queue handling, Nivedita Singhvi |
| Next by Thread: | Re: question about linux tcp request queue handling, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |