From: Jakub Jelinek <jakub@redhat.com>
To: Chris Wedgwood <cw@f00f.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: sendfile64?
Date: Tue, 20 Feb 2001 05:53:33 -0500 [thread overview]
Message-ID: <20010220055333.S16592@devserv.devel.redhat.com> (raw)
In-Reply-To: <20010220015518.B12073@convergence.de> <20010220145123.A1609@metastasis.f00f.org>
In-Reply-To: <20010220145123.A1609@metastasis.f00f.org>; from cw@f00f.org on Tue, Feb 20, 2001 at 02:51:24PM +1300
On Tue, Feb 20, 2001 at 02:51:24PM +1300, Chris Wedgwood wrote:
> Why isn't there a sendfile64?
>
> because nobody has implemented on -- arguably it's not needed; the
> different between:
>
> sendfile64(...)
>
> and
>
> while(blah){
> sendfile( ... 1G or so ...)
> }
>
> probably won't be detectable anyhow. I see no reason why sendfile64
> should be purely user-space (then again, I see no reason why not to
> extend the kernel API as is, but last time I tested it is was busted
> WRT signals so I would rather that be fixed before further
> proliferation there).
Wrong. sendfile takes a pointer to off_t, not loff_t, so you cannot replace
sendfile64 with multiple sendfile's if offset is non-NULL from userland.
It simply won't work properly on big files (no matter what size you transfer
at a time).
Jakub
next prev parent reply other threads:[~2001-02-20 10:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-20 0:55 sendfile64? Felix von Leitner
2001-02-20 1:51 ` sendfile64? Chris Wedgwood
2001-02-20 10:53 ` Jakub Jelinek [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-31 15:53 sendfile64()? Roy Sigurd Karlsbakk
2002-05-31 16:28 ` sendfile64()? Mark Mielke
2002-06-04 13:58 ` sendfile64()? Artur Frysiak
2002-06-04 14:24 ` sendfile64()? Matti Aarnio
2002-06-04 16:36 ` sendfile64()? Ingo Oeser
2002-06-04 17:31 ` sendfile64()? Benjamin LaHaise
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=20010220055333.S16592@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=cw@f00f.org \
--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