man2/socketcall.2

   1 .\" Copyright (c) 1995 Michael Chastain (mec@shell.portal.com), 15 April 1995.
   2 .\"
   3 .\" This is free documentation; you can redistribute it and/or
   4 .\" modify it under the terms of the GNU General Public License as
   5 .\" published by the Free Software Foundation; either version 2 of
   6 .\" the License, or (at your option) any later version.
   7 .\"
   8 .\" The GNU General Public License's references to "object code"
   9 .\" and "executables" are to be interpreted as the output of any
  10 .\" document formatting or typesetting system, including
  11 .\" intermediate and printed output.
  12 .\"
  13 .\" This manual is distributed in the hope that it will be useful,
  14 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
  15 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
  16 .\" GNU General Public License for more details.
  17 .\"
  18 .\" You should have received a copy of the GNU General Public
  19 .\" License along with this manual; if not, see
  20 .\" <http://www.gnu.org/licenses/>.
  21 .\"
  22 .\" Modified Tue Oct 22 22:11:53 1996 by Eric S. Raymond <esr@thyrsus.com>
  23 .TH SOCKETCALL 2 2012-10-16 "Linux" "Linux Programmer's Manual"
  24 .SH NAME
  25 socketcall \- socket system calls
  26 .SH SYNOPSIS
  27 .BI "int socketcall(int " call ", unsigned long *" args );
  28 .SH DESCRIPTION
  29 .BR socketcall ()
  30 is a common kernel entry point for the socket system calls.
  31 .I call
  32 determines which socket function to invoke.
  33 .I args
  34 points to a block containing the actual arguments,
  35 which are passed through to the appropriate call.
  36 .PP
  37 User programs should call the appropriate functions by their usual names.
  38 Only standard library implementors and kernel hackers need to know about
  39 .BR socketcall ().
  40 .SH CONFORMING TO
  41 This call is specific to Linux, and should not be used in programs
  42 intended to be portable.
  43 .SH NOTES
  44 On a some architectures\(emfor example, x86-64 and ARM\(emthere is no
  45 .BR socketcall ()
  46 system call; instead
  47 .BR socket (2),
  48 .BR accept (2),
  49 .BR bind (2),
  50 and so on really are implemented as separate system calls.
  51 .SH SEE ALSO
  52 .BR accept (2),
  53 .BR bind (2),
  54 .BR connect (2),
  55 .BR getpeername (2),
  56 .BR getsockname (2),
  57 .BR getsockopt (2),
  58 .BR listen (2),
  59 .BR recv (2),
  60 .BR recvfrom (2),
  61 .BR recvmsg (2),
  62 .BR send (2),
  63 .BR sendmsg (2),
  64 .BR sendto (2),
  65 .BR setsockopt (2),
  66 .BR shutdown (2),
  67 .BR socket (2),
  68 .BR socketpair (2)