linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Jon Goldberg <jgoldberg@neocore.com>
Cc: Andrew Morton <akpm@digeo.com>, linux-mm@kvack.org
Subject: RE: Porting to from Solaris 64bit to Linux 32B - 36B.
Date: Wed, 20 Nov 2002 16:31:40 -0200 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.44L.0211201629170.4103-100000@imladris.surriel.com> (raw)
In-Reply-To: <C5BF7C2C6ADF24448763CC46235FB3A691C833@ulysses.neocore.com>

On Wed, 20 Nov 2002, Jon Goldberg wrote:

> 	Will that return a 64 bit offset pointer to the file or just let
> me map 3-4GB in a 10 BG file with a 64 bit offset pointer.  What I would
> like to do is mmap the full 10GB file and walk it with a 64 bit pointer
> knowing that not more that 2GB can be in memory.

How exactly do you think the mythical mmap64() would ever work
on 32 bit machines ?

It is impossible to map 10 GB of file into 2-3 GB of virtual
address space.

Maybe there is a userspace library to emulate things with (slow)
64 bit pointers, etc... but it is fundamentally impossible to do
in kernel space.

regards,

Rik
-- 
Bravely reimplemented by the knights who say "NIH".
http://www.surriel.com/		http://guru.conectiva.com/
Current spamtrap:  <a href=mailto:"october@surriel.com">october@surriel.com</a>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2002-11-20 18:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-20 17:36 Jon Goldberg
2002-11-20 18:31 ` Rik van Riel [this message]
     [not found] <C5BF7C2C6ADF24448763CC46235FB3A691C82E@ulysses.neocore.com>
2002-11-20  0:24 ` Rik van Riel
2002-11-20  8:33   ` Andrew Morton

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=Pine.LNX.4.44L.0211201629170.4103-100000@imladris.surriel.com \
    --to=riel@conectiva.com.br \
    --cc=akpm@digeo.com \
    --cc=jgoldberg@neocore.com \
    --cc=linux-mm@kvack.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