public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Maas <dmaas@maasdigital.com>
To: davem@redhat.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: sendfile(2) behaviour has changed?
Date: Sun, 20 Oct 2002 05:50:20 -0400	[thread overview]
Message-ID: <20021020055020.A3289@morpheus> (raw)

>> It really needs a new interface for recvfile/copyfile/whatever
>> anyway, as you can only specify an off_t for the from fd at
>> present.
>   
> Ummm, you can use lseek() on the 'to' fd perhaps?

Wouldn't that be non-atomic and therefore likely to cause problems
with concurrent writes?

Regards,
Dan

             reply	other threads:[~2002-10-20  9:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20  9:50 Dan Maas [this message]
2002-10-24 22:37 ` sendfile(2) behaviour has changed? Jamie Lokier
  -- strict thread matches above, loose matches on Subject: below --
2002-10-16  8:49 sendfile(2) behaviour has changed ? Zilvinas Valinskas
2002-10-16  9:10 ` Matti Aarnio
2002-10-16  9:59   ` David S. Miller
2002-10-16 10:25     ` bert hubert
2002-10-17 20:51     ` James Antill
2002-10-17 22:41       ` David S. Miller
2002-10-17 23:23         ` James Antill

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=20021020055020.A3289@morpheus \
    --to=dmaas@maasdigital.com \
    --cc=davem@redhat.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