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
LEARN ABOUT OPENDARWIN
sockstat
SOCKSTAT(1) BSD General Commands Manual SOCKSTAT(1)
NAME
sockstat -- list open sockets
SYNOPSIS
sockstat [-clh] [-p ports] [-P pid|process] [-U uid|user] [-G gid|group]
DESCRIPTION
The sockstat command lists open Internet or UNIX domain sockets.
The following options are available:
-c Show connected sockets.
-l Show listening sockets.
-h Show a usage summary.
-p ports Only show Internet sockets if either the local or foreign port number is on the specified list. The ports argument is a comma-
separated list of port numbers and ranges specified as first and last port separated by a dash.
-P pid|process
Only show sockets of the specified pid|process. The pid|process argument is a process name or pid.
-U uid|user
Only show sockets of the specified uid|user. The uid|user argument is a username or uid.
-G gid|group
Only show sockets of the specified gid|group. The gid|group argument is a groupname or gid.
If neither -c or -l is specified, sockstat will list both listening and connected sockets.
The information listed for each socket is:
USER The user who owns the socket.
COMMAND The command which holds the socket.
PID The process ID of the command which holds the socket.
FD The file descriptor number of the socket.
PROTO The transport protocol associated with the socket for Internet sockets, or the type of socket (stream or datagram) for UNIX
sockets.
LOCAL ADDRESS For Internet sockets, this is the address the local end of the socket is bound to (see getsockname(2)). For bound UNIX
sockets, it is the socket's filename. For other UNIX sockets, it is a right arrow followed by the endpoint's filename, or
``??'' if the endpoint could not be determined.
FOREIGN ADDRESS (Internet sockets only) The address the foreign end of the socket is bound to (see getpeername(2)).
SEE ALSO
netstat(1), protocols(5)
HISTORY
The sockstat command appeared in FreeBSD 3.1.
AUTHORS
The sockstat command and this manual page were written by Dag-Erling Smorgrav <des@FreeBSD.org>.
The sockstat command was ported to Linux by William Pitcock <nenolod@nenolod.net>.
BSD May 18, 2008 BSD