How many packets can be written into Kernel sockets per second?

Login or Register to Ask a Question and Join Our Community

How many packets can be written into Kernel sockets per second?

Tags

Login to Discuss or Reply to this Discussion in Our Community

Top Forums UNIX for Advanced & Expert Users How many packets can be written into Kernel sockets per second?

04-29-2016

Registered User

6, 0

Join Date: Sep 2010

Last Activity: 29 April 2016, 7:56 PM EDT

Location: Bangalore

Posts: 6

Thanks Given: 0

Thanked 0 Times in 0 Posts

How many packets can be written into Kernel sockets per second?

Hi,

Its been a long time since i programmed a multithreaded application that can do Tx and Rx of datagrams over unix sockets.

I well remember that though the threads were efficiently designed to be independent of each other, and was writing to different sockets, there was a limitation , which i remember that only 3000 approximate datagrams/packets can be sent/received between the host application and the kernel - which i came to know from some forums, and infact, our timers used to expire due to non-reception of approx >3000 packets if it was configured - reason being the kernel to host transfer of the packets were slow.

Before i could attempt figuring out that again, wanted to ask if anyone knows a theoretical limitation seen by the linux kernels?
In other terms, what is the max data transfer rate between the Kernel space and user space through the various IPC mechanisms?

If i don't get to know that, i may end up doing an assumption.

binnyjeshan

View Public Profile for binnyjeshan

Find all posts by binnyjeshan

Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Linux

Unload kernel module at boot time (Debian Wheezy 7.2, 3.2.0-4-686-pae kernel)

Hi everyone, I am trying to prevent the ehci_hcd kernel module to load at boot time. Here's what I've tried so far: 1) Add the following line to /etc/modprobe.d/blacklist.conf (as suggested here): 2) Blacklisted the module by adding the following string to 3) Tried to blacklist the module...

2. Programming

Why am i getting these strange packets while running my packet capture module written in c.?

I have made an packet capture application running on intel machine, it is capturing packets with src address- 17.0.0.0 destination ip- 66.0.0.0, source port- 0, destination port- 0, and protocol- 0 what does these packets mean ? The code written to interpreter captured bytes is given below....

3. Solaris

syslog is not getting written

hi all syslog is not getting written. i am getting following two logs snmpd.log & authlog logs. please tell what are two logs snmpd.log & authlog logs. why syslog is not written.

4. Programming

c++, raw sockets, stopping kernel write in header?

Hi, im trying to lern about raw sockets with my debian and c++. Tried to make a icmp and tcp packet and send it with sendto. Checked on wireshark and recognized that kernel changed my headers. So searched about stopping the kernel change the header and tried it with setsockopt, like said in at this...

5. Solaris

Which file is read by kernel to set its default system kernel parameters values?

Hi gurus Could anybody tell me which file is read by kernel to set its default system kernal parameters values in solaris. Here I am not taking about /etc/system file which is used to load kernal modules or to change any default system kernal parameter value Is it /dev/kmem file or something...

6. SuSE

max number of slabs per kernel module (kernel 2.6.17, suse)

Hi All, Is there a max number of slabs that can be used per kernel module? I'm having a tough time finding out that kind of information, but the array 'node_zonelists' (mmzone.h) has a size of 5. I just want to avoid buffer overruns and other bad stuff. Cheers, Brendan

7. IP Networking

counting the packets

there are a number of clients connected to a server.... how can i count that each clients recieve ...? how do i moniter the activity of the client..?

8. Programming

Packets Getting Lost

I am working on a project, which has the following type of hardware setup. A special hardware device is receiving data from an external network interface. So we can have multiple such a hardware devices. Now these hardware devices will route the captured incoming data through the external...

9. UNIX for Dummies Questions & Answers

File being used/written

Hello, Which command in unix can tell whether a file is being used/written by another process. e.g. If one process is copying a very big file in some directory and there is another cronjob process which checks for a new file and in this directory and process the file. I want to check, if the...

Login or Register to Ask a Question

LEARN ABOUT OPENSOLARIS

dbus-cleanup-sockets

dbus-cleanup-sockets(1) 					   User Commands					   dbus-cleanup-sockets(1)

NAME

       dbus-cleanup-sockets - clean up leftover sockets in a directory

SYNOPSIS

       dbus-cleanup-sockets [--help] [--version] [directory]

DESCRIPTION

       The dbus-cleanup-sockets command cleans up unused D-Bus connection sockets.

       If  given no arguments, dbus-cleanup-sockets cleans up sockets in the standard default socket directory for the per-user-login-session mes-
       sage bus; this is usually /tmp.	Optionally, you can pass a different directory on the command line.

       On Linux, this program is essentially useless, because D-Bus defaults to using "abstract sockets" that exist only in memory and don't  have
       a corresponding file in /tmp.

       On  most  other	flavors  of UNIX, it is possible for the socket files to leak when programs using D-Bus exit abnormally or without closing
       their D-Bus connections. Thus, it might be interesting to run dbus-cleanup-sockets in a cron job to clean up any leaked	sockets.   Or  you
       can just ignore the leaked sockets, they are not really hurting anything, other than cluttering the /tmp directory.

       See http://www.freedesktop.org/software/dbus/ for more information.

OPTIONS

       The following options are supported:

       --help

	   Show help information on standard output and exit.

       --version

	   Print the version of dbus-cleanup-sockets

OPERANDS

       The following operands are supported:

       directory       Clean up sockets in the specified directory rather than the default socket directory.

EXIT STATUS

       The following exit values are returned:

       0	Application exited successfully

       >0	Application exited with failure

FILES

       The following files are used by this application:

       /usr/bin/dbus-cleanup-sockets   Executable for dbus-cleanup-sockets

       /tmp			       Default location for D-Bus connection sockets

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWdbus			   |
       +-----------------------------+-----------------------------+
       |Interface stability	     |Volatile			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       dbus-daemon(1), dbus-launch(1), dbus-monitor(1), dbus-send(1), dbus-uuidgen(1), libdbus-glib-1(3), attributes(5)

NOTES

       For authorship information refer to http://www.freedesktop.org/software/dbus/doc/AUTHORS.  Updated by Brian Cameron, Sun Microsystems Inc.,
       2007.

       dbus-cleanup-sockets was adapted by Havoc Pennington from linc-cleanup-sockets written by Michael Meeks.  Documentation	updated  by  Brian
       Cameron, Sun Microsystems Inc., 2007.

       Please send bug reports to the D-Bus mailing list or bug tracker, see http://www.freedesktop.org/software/dbus/

SunOS 5.11							    19 Nov 2007 					   dbus-cleanup-sockets(1)