From: Rik van Riel <H.H.vanRiel@phys.uu.nl>
To: "Eric W. Biederman" <ebiederm+eric@npwt.net>
Cc: linux-mm@kvack.org
Subject: Re: Fixing private mappings
Date: Thu, 23 Apr 1998 10:28:50 +0200 (MET DST) [thread overview]
Message-ID: <Pine.LNX.3.91.980423102626.4620C-100000@mirkwood.dummy.home> (raw)
In-Reply-To: <m1ra2pnn3c.fsf@flinx.npwt.net>
On 23 Apr 1998, Eric W. Biederman wrote:
> A slightly more generic solution would be to introduce a new ``inode''
> that new it was a copy of the old inode but at a different offset. If
> these new ``inodes'' would then have a linked list of their own, that
> could be followed for update purposes.
>
> Extra inodes for files could also be extended to allow an offset at
> say 4TB or so into a file so that we can handle any sized file.
> Though obviously you can't cache it all at once, but you could cache
> any piece ;)
This is a nice idea indeed. Maybe we could even use the
'extra inodes' idea to implement arbitrarily large files
on _any_ architecture...
When the on-disk maximum size is reached, just grab a
slave inode and start on part two.
The same for in-memory inodes, but there the maximum
size may be different.
Rik.
+-------------------------------------------+--------------------------+
| Linux: - LinuxHQ MM-patches page | Scouting webmaster |
| - kswapd ask-him & complain-to guy | Vries cubscout leader |
| http://www.phys.uu.nl/~riel/ | <H.H.vanRiel@phys.uu.nl> |
+-------------------------------------------+--------------------------+
next prev parent reply other threads:[~1998-04-23 9:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-23 5:06 Eric W. Biederman
1998-04-23 8:28 ` Rik van Riel [this message]
1998-04-23 15:12 ` Benjamin C.R. LaHaise
1998-04-23 22:03 ` Eric W. Biederman
1998-04-24 20:37 ` Stephen C. Tweedie
1998-04-25 5:30 ` Eric W. Biederman
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.3.91.980423102626.4620C-100000@mirkwood.dummy.home \
--to=h.h.vanriel@phys.uu.nl \
--cc=ebiederm+eric@npwt.net \
--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