From: "Dan Maas" <dmaas@dcine.com>
To: "Chris Wedgwood" <cw@f00f.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: LFS Support for Sendfile
Date: Sun, 3 Mar 2002 00:08:45 -0500 [thread overview]
Message-ID: <02bb01c1c271$7f717700$1a01a8c0@allyourbase> (raw)
In-Reply-To: <fa.inaf1vv.one4p5@ifi.uio.no> <fa.esfhmsv.bku814@ifi.uio.no>
> [sendfile(2)] as defined does not support LFS.
>
> I wonder does it really need to? I mean, a loop calling sendfile for
> 2GB (or whatever) at a time is almost as good, if not better in some
> ways.
The 'count' parameter is not the problem, it's the 'offset'. You can't send
any data beyond 2GB from the beginning of the file...
And in fact just two days ago I was in a situation where this would have
been desirable - I was sending parts of a captured DV video stream (the file
was 6GB)...
Regards,
Dan
next parent reply other threads:[~2002-03-03 5:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.inaf1vv.one4p5@ifi.uio.no>
[not found] ` <fa.esfhmsv.bku814@ifi.uio.no>
2002-03-03 5:08 ` Dan Maas [this message]
2002-03-03 5:34 ` LFS Support for Sendfile Andrew Morton
2002-02-28 0:27 Doug O'Neil
2002-02-28 1:22 ` Doug McNaught
2002-02-28 8:03 ` Matti Aarnio
2002-03-02 22:24 ` Chris Wedgwood
2002-03-03 12:36 ` Hans Reiser
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='02bb01c1c271$7f717700$1a01a8c0@allyourbase' \
--to=dmaas@dcine.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