public inbox for linux-fsdevel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: "Joseph D. Wagner" <theman@josephdwagner.info>
Cc: "'Jamie Lokier'" <jamie@shareable.org>,
	"'maximilian attems'" <janitor@sternwelten.at>,
	linux-fsdevel@vger.kernel.org
Subject: RE: Does sendfile() copy extended attributes?
Date: Sun, 21 Dec 2003 14:44:30 -0500	[thread overview]
Message-ID: <1072035869.19157.52.camel@zaphod> (raw)
In-Reply-To: <000001c3c7f9$16e052d0$0201a8c0@joe>

On Sun, 2003-12-21 at 14:31, Joseph D. Wagner wrote:
> > I think you read what I wrote the wrong way.  Let me rephrase it:
> > How can you know that function does not call an external program to
> > perform its action?
> 
> Again, sendfile() is a KERNEL function.

unless you use the syscall macros to do the syscall interrupt yourself,
you are calling the libc wrapper for the system call, not the system
call itself.




  reply	other threads:[~2003-12-21 19:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 17:39 Does sendfile() copy extended attributes? Joseph D. Wagner
2003-12-15  5:43 ` Shaya Potter
2003-12-15  5:46   ` Jeff Garzik
2003-12-15  5:49     ` Shaya Potter
2003-12-15  5:55       ` Jeff Garzik
2003-12-15  5:59         ` Shaya Potter
2003-12-15 17:16 ` Bryan Henderson
2003-12-15 20:15   ` Joseph D. Wagner
2003-12-15 21:28     ` Jamie Lokier
2003-12-16  4:28       ` Joseph D. Wagner
2003-12-19 16:37         ` maximilian attems
2003-12-20 12:19           ` Joseph D. Wagner
2003-12-20 20:40             ` Jamie Lokier
2003-12-21 11:01               ` Joseph D. Wagner
2003-12-21 11:50                 ` Jamie Lokier
2003-12-21 19:31                   ` Joseph D. Wagner
2003-12-21 19:44                     ` Shaya Potter [this message]
2003-12-21 19:51                       ` Jamie Lokier

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=1072035869.19157.52.camel@zaphod \
    --to=spotter@cs.columbia.edu \
    --cc=jamie@shareable.org \
    --cc=janitor@sternwelten.at \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=theman@josephdwagner.info \
    /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