From: Nat Ersoz <nat.ersoz@myrio.com>
To: David Wuertele <dave-gnus@bfnet.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: Why doesn't UNIX/DGRAM socket allow sending more than 11 bytes w/o receiving?
Date: Fri, 23 May 2003 08:24:50 -0700 [thread overview]
Message-ID: <3ECE3D42.4010801@myrio.com> (raw)
In-Reply-To: <m3adg67i2f.fsf@bfnet.com>
Well, this is my first experience with UNIX sockets (though I've plenty
of experience with IP sockets). I've always wondered what I what the
use of UNIX sockets was - so I took a look.
Simply, it looks like after sending 11 datagrams, the OS is blocking the
send() call until a receiver empties out some of the buffer space before
proceeding. Changing the size of buff[] to 2048, still allows for 11
buffers to be sent prior to blocking.
Changing the buffer size to 1024*32 however, allows only 2 buffers to be
sent before blocking.
This appears to conform to proper UNIX socket behavior, from everthing I
can find. Does this seem like improper behavior?
Nat
David Wuertele wrote:
>Question: Why does this program crap out after 11 bytes?
>The UNIX/DGRAM receive buffer should be 64Kbytes. I expect this
>program to be able to use it all before blocking. But it blocks
>after only 11.
>
>// dgramtest.c
>// creates two unix/dgram sockets, connects them, sends a byte at a
>// time without recv()ing anything. demonstrates strange behavior on
>// Linux 2.4.18 (RedHat 8.0)
>
>#include <sys/types.h>
>#include <sys/stat.h>
>#include <sys/socket.h>
>#include <sys/un.h>
>#include <fcntl.h>
>#include <unistd.h>
>#include <stdio.h>
>#include <string.h>
>#include <errno.h>
>
>///////////////////////////////////////////////////////////////////////////////
>// module socktest #defines
>#define INPUT_SOCKET_NAME "/tmp/sockinput"
>#define OUTPUT_SOCKET_NAME "/tmp/sockoutput"
>#define BUFF_SIZE (1)
>
>///////////////////////////////////////////////////////////////////////////////
>// module socktest function Bail
>static int Bail(const char * pString)
>{
> perror(pString);
> return 1;
>}
>
>///////////////////////////////////////////////////////////////////////////////
>// module socktest function main
>int main(int argc, const char ** argv)
>{
> sockaddr_un addressInput;
> addressInput.sun_family = AF_UNIX;
> strcpy(addressInput.sun_path, INPUT_SOCKET_NAME);
>
> sockaddr_un addressOutput;
> addressOutput.sun_family = AF_UNIX;
> strcpy(addressOutput.sun_path, OUTPUT_SOCKET_NAME);
>
> int sockInput = socket(PF_UNIX, SOCK_DGRAM, 0);
> if (-1 == sockInput) return Bail("Failed to create input socket");
>
> int sockOutput = socket(PF_UNIX, SOCK_DGRAM, 0);
> if (-1 == sockOutput) return Bail("Failed to create output socket");
>
> // name (bind) the 2 sockets
> unlink(INPUT_SOCKET_NAME);
> unlink(OUTPUT_SOCKET_NAME);
> if (-1 == bind(sockInput, (const sockaddr *)&addressInput, sizeof(sockaddr_un))) return Bail("Failed to bind input socket");
> if (-1 == bind(sockOutput, (const sockaddr *)&addressOutput, sizeof(sockaddr_un))) return Bail("Failed to bind output socket");
>
> // connect the output socket to the input address
> if (-1 == connect(sockOutput, (const sockaddr *)&addressInput, sizeof(sockaddr_un))) return Bail("Failed to connect output to input socket");
>
> // now see how many sends we can do before send blocks
> char buff[BUFF_SIZE];
> int nNumBytes = 0;
> int nNumSends = 0;
> while (1)
> {
> if (sizeof(buff) != send(sockOutput, buff, sizeof(buff), 0)) break;
> //DON'T RECEIVE! This is the test. We should crap out after
> //getting 64K bytes.
> //if (sizeof(buff) != recv(sockInput, buff, sizeof(buff), 0)) break;
> nNumSends++; nNumBytes+= sizeof(buff);
> printf("Send %d, %d total bytes\n", nNumSends, nNumBytes); fflush(stdout);
> }
>
> printf("Exiting after %d sends with %d total bytes\n", nNumSends, nNumBytes);
> perror("Error");
> return 0;
>}
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-c-programming" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
_________________________________________
Nat Ersoz nat.ersoz@myrio.com -o)
Myrio Corporation Phone: 425.897.7278 /\\
3500 Carillon Point Cell: 425.417.5182 _\_V
Kirkland, WA 98033 Fax: 425.897.5600
prev parent reply other threads:[~2003-05-23 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 1:39 Why doesn't UNIX/DGRAM socket allow sending more than 11 bytes w/o receiving? David Wuertele
2003-05-23 15:24 ` Nat Ersoz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3ECE3D42.4010801@myrio.com \
--to=nat.ersoz@myrio.com \
--cc=dave-gnus@bfnet.com \
--cc=linux-c-programming@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).