Skip to main content

Use of Select() System Call In Linux To make a non-blocking connect()

About Select system call
The  select() function shall examine the file descriptor sets whose addresses are passed in the readfds, writefds,
       and errorfds parameters to see whether some of their descriptors are ready for reading, are ready for  writing,  or
       have an exceptional condition pending, respectively.
  int select(int nfds, fd_set *restrict readfds,
              fd_set *restrict writefds, fd_set *restrict errorfds,
              struct timeval *restrict timeout);
There are many usages of select() system call, Here is one usage in networking applications, The use of select system call is to make non-blocking call in Linux.
how to make a non-blocking connect() in Linux

1. create socket using socket(),

2. set the file descriptor to non-blocking mode using fcntl(2)
   fnctl (fd, SETFL, fcntl(fd, GETFL) | O_NONBLOCK)

3. call connect() - since you have set the socket to non-blocking, it will
return right away with a result of EINPROGRESS.

4.  Now

   a) Go into a loop and keep calling connect() - as long as it
       has not completed it will return EALREADY (see man page for
       connect()).  This is simple but not a good solution. check below solution
       using select to avoid loop wait.
OR
   b) Use select(2), selecting the socket for write.  When the connect is
       finished, the select should return and show the socket as writeable.
       Using select() can be tricky, but will be more efficient, since
       select() will block until the connect has finished and you are not
       wasting CPU in a tight loop.

       /* No loop required */
       fd_set write_set;
       FD_ZERO(write_set);
       FD_SET(write_set, fd);
       select (fd+1, 0, write_set, 0, 0);

File descriptor masks of type fd_set can be  initialized  and  tested  with  FD_CLR(),  FD_ISSET(),  FD_SET(),  and
   
     FD_SET(fd,  fdsetp)  shall add the file descriptor fd to the set pointed to by fdsetp. If the file descriptor fd is
       already in this set, there shall be no effect on the set, nor will an error be returned.
     FD_ZERO(fdsetp) shall initialize the descriptor set pointed to by fdsetp to the null set. No error is  returned  if
       the set is not empty at the time FD_ZERO() is invoked.
 The  original  Standard  can  be  obtained  online at http://www.opengroup.org/unix/online.html

Comments

Popular posts from this blog

Dotnet, .Net 3.5, 2.0, C# Interview Questions

Few questions on dotnet, C# 2.0, 3.5 On Object oriented concepts 1)What is inheritance with e.g 2)What is polymorphism -function overloading -Function overriding -virtual keyword use -Static keyword and use -Abstract classes -Interface -Object 3)What is threading and how do we use in realtime application(cognizant) 4)What is threadpooling, lock, monitor(write code sample) 5)Architecture of current project 6)Session state, diffrent types of state management. 7)What is Application_Start, how it works. 8)Type of authentication in asp.net 9)How to configure ASP.NET application. 10) What is Impersonation. 11) What is WebService, WSDL, UDDI, Discovery, asmx files. 12) How to implement WebService and use it. 13) When to use WebServices. 14) WPF, how to implement(BOA) 15) Testing concvepts. 16) Test attributes 17) Flow of Automation Test Method execution 18) Features of dotnet 3.5 19) CLR, garbage collection 20) Finally block 21) Manifest, Metadata, MSIL 22) Assemblies, Type of assemblies, str...

Remote debugging for ARM target board

Remote debugging for ARM target board With GDB one can both trace and modify code and data flow, and otherwise analyze the behavior of code, without explicitly changing any of it. Rather than run a full-blown instance of GDB on the target platform, you can use GDBserver , a program that lets you run GDB on a different machine than the one on which your program is running. The advantage of using GDBserver is that it needs just a fraction of the target resources that GDB consumes, because it implements only the low-level functionality of the debugger -- namely setting breakpoints and accessing the target processor registers and read/write application memory. GDBserver takes control of the application being debugged, and then waits for instructions from a remote instance of GDB running on a development workstation. Remote target needs to have debugging stub (gdbserver), The gdbserver is also referred to as the 'stub' and must be cross-compiled for that targ...