mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Amber Palekar <amber_palekar@yahoo.com>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Again:syscall from modules
Date: Tue, 25 Dec 2001 19:37:27 +0100	[thread overview]
Message-ID: <15400.51047.900520.331948@charged.uio.no> (raw)
In-Reply-To: <20011225131441.60811.qmail@web20306.mail.yahoo.com>
In-Reply-To: <shssn9zv43k.fsf@charged.uio.no> <20011225131441.60811.qmail@web20306.mail.yahoo.com>

>>>>> " " == Amber Palekar <amber_palekar@yahoo.com> writes:

     >  Hi,
 
    >> Just use sock_sendmsg() and sock_recvmsg() directly.  They are
    >> both exported in netsyms.c.
     >   Is there any specific reason behind not exporting
     > sys_sendto and sys_recvfrom ??

Why would you want to do that when you already have a better kernel
interface available?

The sys_sendto, sys_recvfrom references the sockets by file handle,
something which requires an extra lookup operation to map the file
handle to socket struct.
OTOH sock_sendmsg(), sock_recvmesg() provides exactly the same
functionality, but takes a pointer to the kernel socket structure as
the argument.

Cheers,
  Trond

      parent reply	other threads:[~2001-12-25 18:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-25 11:31 syscall " Amber Palekar
2001-12-25 13:09 ` Trond Myklebust
2001-12-25 13:14   ` Again:syscall " Amber Palekar
2001-12-27 15:54     ` Terje Eggestad
2001-12-27 16:04     ` Terje Eggestad
2001-12-27 18:57     ` Trond Myklebust
2001-12-28 15:41       ` Ralf Baechle
2001-12-28 15:48       ` Trond Myklebust
2001-12-28 16:26         ` Ralf Baechle
2001-12-25 18:37   ` Trond Myklebust [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=15400.51047.900520.331948@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=amber_palekar@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®