07-06-2010
msleep makes the process wait for a given amount of milliseconds.
I expect this not to slow down the requests, since this interface is by definition asynchronous. Anyway, removing that call does not help to avoid the problem, since repeated calls to easy_perform on single easy_handles are still faster...
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi expert,
Need some help on network interface issue..
I have added 2 x NIC card onto the Ultra 2 system recently and configured as hme1 and hme2. I have unconfigured the onboard hme0 network interface and it was running fine till few days later, i keep recieving error messages showing hme0... (6 Replies)
Discussion started by: sc2005
6 Replies
2. AIX
Hi every body,
I have a Fiber Channel interface (fcs2) in AIX 5.2. This interface was fine & up but for some reason I could not return this interface UP again after I set it DOWN.
When I tried to set this interface UP I encountered the following error:
Method error... (7 Replies)
Discussion started by: aldowsary
7 Replies
3. UNIX for Dummies Questions & Answers
My system info is show below:-
#uname -a
SunOS qfserver 5.8 Generic_117350-29 sun4u sparc SUNW,Sun-Blade-2500
and I have two network card as shown below:-
#ifconfig -a
lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
bge0:... (1 Reply)
Discussion started by: sarifudin
1 Replies
4. UNIX for Advanced & Expert Users
hi all,
i have problem with my box,
until now i can't investigate the root cause of my issue at my box.
here the problem.
i have a box as a squid server just forward all request packet from one interface and receive the packet then forward to client at the same interface. but after 5 hours i... (1 Reply)
Discussion started by: tindasz
1 Replies
5. AIX
Hello,
I need "devices.common.IBM.ml 1.4.0.0 C F Multi Link Interface Runtime" to be installed on my machine.
I need it for two SAN cards to work correctly.
Where do I get it ?
thanks
Vilius (1 Reply)
Discussion started by: vilius
1 Replies
6. Debian
Hi, i have problems with an installation of Debian i386 505 in a pc. The hardware it is a mother soyo with a chipset via.
When i install the xorg, the installation it`s succesfull, but when i type startx, the pc don`t respond.
I am from Argentina and my English it isn`t good. Sorry. (0 Replies)
Discussion started by: Kritar
0 Replies
7. Solaris
HI,
genunix: NOTICE: ce0: xcvr addr:0x01 - link up 100 Mbps half duplex
genunix: WARNING: ce0: fault detected external to device; service degraded
genunix: WARNING: ce0: xcvr addr:0x01 - link down
genunix: NOTICE: ce0: fault cleared external to device; service available
genunix: ... (4 Replies)
Discussion started by: sunnybee
4 Replies
8. IP Networking
Hi,
We currently operate a DHCP Server on Vxworks system.
It seems that the server is functioning only over the boot interface.
While trying to use it on a different interface the DHCP client messages seems to reach the interface but stay without response.
From a... (1 Reply)
Discussion started by: zohara
1 Replies
9. Red Hat
libcurl.so.4: cannot open shared object file: No such file or directory
ERROR: Loading network library (net.so) failed!
Press Q to shut down the server!
http://a1108.hizliresim.com/11/8/17/8183.jpg
What must I do ? :wall: (14 Replies)
Discussion started by: Stark0010
14 Replies
10. IP Networking
Hello,
I wanted to setup routing certain traffic (http/s) out via a second (faster) interface, like described in the following docs (may not post urls):
linux-ip.net /html/adv-multi-internet.html
thegeekstuff.com /2014/08/add-route-ip-command/
I already had this working years ago on... (0 Replies)
Discussion started by: hyphan
0 Replies
nfsiod(8) System Manager's Manual nfsiod(8)
NAME
nfsiod, biod - The local NFS compatible asynchronous I/O daemon
SYNOPSIS
nfsiod [ numthreads ]
DESCRIPTION
The nfsiod daemon runs on an NFS compatible client machine and spawns several IO threads to service asynchronous I/O requests to its
server. The I/O threads improve performance of both NFS reads and writes. Both try to enlist the aid of an idle I/O thread. If none is
available, the process itself issues the request to the server and waits for the reply.
The optimum number of I/O threads to run depends on many variables, such as how quickly the client will be writing, how many files will be
accessed simultaneously, and the behaviour of the NFS server. For use with a Tru64 UNIX server, 7 is a good number of I/O threads for most
systems.
When reading, if the client believes the process is reading a file sequentially, it requests an I/O thread to read a block ahead of what
the process is currently requesting. If the readahead completes before the process asks for that block, then the subsequent read system
call for that data completes immediately and does not have to wait for the NFS request to complete. Read ahead will be triggered again so
the read may find that next block available as well.
When writing a file, the client takes the process's data, passes the request to an I/O thread and immediately returns to the process. If
the process is writing data faster than the network or server can process, then eventually all the I/O threads become busy and the process
has to handle a NFS write itself. This means the process has to wait until the server finishes the write. For Tru64 UNIX servers, the NFS
block size is 8Kb and UFS tries to cluster I/O 64Kbs at a time. If the client is running with 7 I/O threads, 8 write requests can be in
progress at once. This allows the client and server to write data 64Kbs at a time and is the reason for recommending 7 I/O threads.
Unlike nfsd, each client thread can use either UDP or TCP. However, if TCP mounts are active, the nfsiod process will time out, close idle
TCP connections, and acknowledge any connections closed by the server.
The nfsiod process is also responsible for syncing the access time and modify times for special files and named pipes (fifos). Because I/O
to these files does not go through the NFS server, NFS clients have to directly update the access time and modify time attributes.
The client threads are implemented as kernel threads; they are part of Process ID 0, not the nfsiod process. The ps axml command displays
idle I/O threads under PID 0. Idle threads will be waiting on nfsiod_wait. Therefore, if 7 I/O threads are configured, only 1 nfsiod
process is displayed in the output from the ps command, although 7 client threads are available to handle NFS requests.
FILES
Specifies the command path Specifies the file for logging NFS activity.
RELATED INFORMATION
Commands: nfsd(8), nfsstat(8)
Daemons: async_daemon(2) delim off
nfsiod(8)