public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: roy@karlsbakk.net
Cc: jes@trained-monkey.org, haveblue@us.ibm.com,
	linux-kernel@vger.kernel.org
Subject: Re: acenic >4gig sendfile problem
Date: Mon, 24 Jun 2002 09:02:06 -0700 (PDT)	[thread overview]
Message-ID: <20020624.090206.44274295.davem@redhat.com> (raw)
In-Reply-To: <200206241755.00082.roy@karlsbakk.net>

   From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
   Date: Mon, 24 Jun 2002 17:54:59 +0200

   sendfile() doesn't support >4gig anyway - does it?
   that's the (yet unimplemented) sendfile64()

Nothing to do with file offsets.  It has to do with what physical page
the file data ends up in which can be anywhere.

  reply	other threads:[~2002-06-24 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-10 21:55 acenic >4gig sendfile problem Dave Hansen
2002-06-24 15:31 ` Jes Sorensen
2002-06-24 15:54   ` Roy Sigurd Karlsbakk
2002-06-24 16:02     ` David S. Miller [this message]
2002-06-25  6:46   ` Dave Hansen

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=20020624.090206.44274295.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=haveblue@us.ibm.com \
    --cc=jes@trained-monkey.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roy@karlsbakk.net \
    /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