03-27-2008
UNIX domain sockets vs FIFOs
Is there a performance advantage of one of these over the other? Obviously, it makes no sense to use normal TCP sockets or UDP sockets w/ the overhead they carry. But what about UNIX domain sockets vs FIFOs? I'd think they'd be very similar, in terms of performance and in terms of how they're manipulated.
I plan on doing non-blocking I/O on these and using select to decide when to read an interface.
Thanks,
Matt Gessner
10 More Discussions You Might Find Interesting
1. IP Networking
hello,
how can we create a domain in unix operating systems. By domain i mean which is used to maintain remote user logins and etc.
cheers (1 Reply)
Discussion started by: vibhory2j
1 Replies
2. UNIX for Dummies Questions & Answers
Hi,
Can I make a UNIX or LINUX machine a member of MS Active Directory 2003?
How?
Regards
Leo (4 Replies)
Discussion started by: Teamplay
4 Replies
3. UNIX for Dummies Questions & Answers
Hiya,
what is the exact command to add a Unix machine to the existing domain?
Is this command different for Linux/HP-Ux?
thanks (3 Replies)
Discussion started by: Wize
3 Replies
4. HP-UX
Hi,
I am having some error handling issues with and fd passed between Independent processes using unix domain sockets (On HPUX).
Here is the scnerio
=================
Step 1: TPC/Client (connect()) ---Connects to ------TCP/Server(Gateway) (server gets fd)
Step 2: ... (2 Replies)
Discussion started by: Debasisb2002
2 Replies
5. Programming
omg i need help so bad. I've been working on a school project for what seems like an eternity and i'm close to deadline. Using FIFO's (i ahve to) to communicate between parent and child proc's. Right now I'm stuck on a read/write.
fifomsg is a struct with int length and char message fields. ... (5 Replies)
Discussion started by: Funktar
5 Replies
6. Programming
Hi, so I've got this program("main") that fork executes another ("user"). These programs communicate through fifos.
One communication is a spawn call, where user passes an executable, main forks and executes it. So, I'm keeping track of all my processes using a task table. After the fork (for... (6 Replies)
Discussion started by: Funktar
6 Replies
7. Linux
This isn't strictly a Linux question, but... I've been working on a project to archive some streaming media for time shifting using 'mplayer' and have been using FIFOs to archive in Ogg Vorbis format:
mkfifo program_name.wav
(mplayer -ao pcm -aofile program_name.wav &)... (0 Replies)
Discussion started by: deckard
0 Replies
8. UNIX for Advanced & Expert Users
How can I make tar read data from a fifo, instead of storing it as a fifo? (8 Replies)
Discussion started by: Corona688
8 Replies
9. UNIX for Advanced & Expert Users
If I use sockets for IPC, and can easily distribute my applications.
UNIX Message Queues are local to the processor.
As I understand it, Message Queues still incur system call overhead, just like socket calls.
What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Discussion started by: zen29sky
2 Replies
10. UNIX for Dummies Questions & Answers
Hi,
i understood that there are several type of sockets: TCP, UDP & Unix.
i wondered, what is the performance advantages of unix socket of the other types?
isn't it equal to use UDP with localhost as destination over unix socket?
Thanks in advance,
Sariel (1 Reply)
Discussion started by: sarielz
1 Replies
UDP(7P) UDP(7P)
NAME
UDP - Internet User Datagram Protocol
SYNOPSIS
DESCRIPTION
UDP is a simple, unreliable datagram protocol used to support the socket type for the internet protocol family. UDP sockets are connec-
tionless, and are normally used with the and calls (see send(2) and recv(2). The call can also be used to simulate a connection (see con-
nect(2). When used in this manner, it fixes the destination for future transmitted packets (in which case the or system calls can be
used), as well as designating the source from which packets are received. The and calls can be used at any time if the source of the mes-
sage is unimportant.
UDP address formats are identical to those used by TCP. In particular, UDP requires a port identifier in addition to the normal Internet
address format. Note that the UDP port domain is separate from the TCP port domain (in other words, a UDP port cannot be connected to a
TCP port).
The default send buffer size for UDP sockets is 65535 bytes. The default receive buffer size for UDP sockets is 2147483647 bytes. The
send and receive buffer sizes for UDP sockets can be set by using the and options of the system call or the and options of the system call.
The maximum size for these buffers is 2147483647 bytes. The maximum receive buffer size may be lowered using the parameter
The maximum message size for a UDP datagram socket is limited by the lesser of the maximum size of an IP datagram and the size of the UDP
datagram socket buffer. The maximum size of an IP datagram limits the maximum message size of a UDP message to 65507 bytes. Therefore,
using the maximum socket buffer size will allow multiple maximum-sized messages to be placed on the send queue. The default inbound and
outbound message size limit for a UDP datagram socket is 65535 bytes.
The maximum message size for a UDP broadcast is limited by the MTU size of the underlying link.
ERRORS
One of the following errors may be returned in if a socket operation fails. For a more detailed list of errors, see the man pages for spe-
cific system calls.
[EISCONN] Attempt to send a datagram with the destination address specified, when the socket is already connected.
[ENOBUFS] No buffer space is available for an internal data structure.
[EADDRINUSE] Attempt to create a socket with a port which has already been allocated.
[EADDRNOTAVAIL] Attempt to create a socket with a network address for which no network interface exists.
AUTHOR
The socket interfaces to UDP were developed by the University of California, Berkeley.
SEE ALSO
ndd(1M). getsockopt(2), recv(2), send(2), socket(2), t_open(3), t_optmgmt(3) inet(7F), socket(7),
RFC 768 User Datagram Protocol
RFC 1122 Requirements for Internet hosts
UDP(7P)