| To: | welk@xxxxxxxxxxxx |
|---|---|
| Subject: | Re: PROBLEM: udp not delivered on special socket receive buffer size |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Wed, 10 Jul 2002 19:15:35 -0700 (PDT) |
| Cc: | netdev@xxxxxxxxxxx, kuznet@xxxxxxxxxxxxx, pekkas@xxxxxxxxxx, gober@xxxxxxxxxxxx |
| In-reply-to: | <200207100945.13002.welk@fokus.gmd.de> |
| References: | <200207100945.13002.welk@fokus.gmd.de> |
| Sender: | owner-netdev@xxxxxxxxxxx |
From: Matthias Welk <welk@xxxxxxxxxxxx> Date: Wed, 10 Jul 2002 09:45:11 +0200 So my question is: Is this a bug or are there any reasons for this magic 831 bytes barrier ? Assuming anything about the meaning of the send/receive buffer sizes, as raw numbers, is going to cause no ends of problems for any application. Under Linux, the size of the socket buffer structure itself (not just the data) is subtracted from the socket buffer size when accounting. That is a perfectly legal thing to do. So the Java code is broken. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [ANNOUNCE] NAPI patches for 2.4.19-rc1, Donald Becker |
|---|---|
| Next by Date: | Re: [ANNOUNCE] NAPI patches for 2.4.19-rc1, Jason Lunz |
| Previous by Thread: | Re: PROBLEM: udp not delivered on special socket receive buffer size, Matthias Welk |
| Next by Thread: | [ANNOUNCE] NAPI patches for 2.4.19-rc1, Jason Lunz |
| Indexes: | [Date] [Thread] [Top] [All Lists] |