From: kanoj@google.engr.sgi.com (Kanoj Sarcar)
To: "Eric W. Biederman" <ebiederm+eric@ccr.net>
Cc: kmorgan@inter-tax.com, linux-mm@kvack.org
Subject: Re: persistent heap design advice
Date: Thu, 8 Apr 1999 19:50:06 -0700 (PDT) [thread overview]
Message-ID: <199904090250.TAA40298@google.engr.sgi.com> (raw)
In-Reply-To: <m1ogkywov1.fsf@flinx.ccr.net> from "Eric W. Biederman" at Apr 8, 99 08:42:58 pm
>
> >>>>> "KM" == Keith Morgan <kmorgan@inter-tax.com> writes:
>
> KM> I am interested in creating a persistent heap library and would
> KM> appreciate any suggestions on how to proceed. The 'persistent heap'
> KM> would be a region of virtual memory backed by a file and could be
> KM> expanded or contracted.
>
> KM> In order to build my 'persistent heap' it seems like I need a
> KM> fundamental facility that isn't provided by Linux. Please correct me if
> KM> I'm wrong! It would be something like mmap() ... but different. The
> KM> facility call it phmap for starters) would:
>
> What do you see missing??
> You obviously need a allactor built on top of your mmaped file but
> besides that I don't see anything missing.
>
> KM> -map virtual addresses to a user-specified file
> mmap MAP_SHARED
And just be careful not to use the same file mmap'ed MAP_SHARED between
"unrelated" processes ...
>
> KM> -coordinate the expansion/contraction of the file and the virtual
> KM> address space
> ftruncate, mmap, munmap
mremap might also come in handy, depending on how you want to handle
out-of-boundary requests ...
Kanoj
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/
prev parent reply other threads:[~1999-04-09 2:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-08 17:23 persistent heap design advice Keith Morgan
1999-04-08 22:00 ` Ingo Oeser
1999-04-09 1:42 ` Eric W. Biederman
1999-04-09 2:50 ` Kanoj Sarcar [this message]
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=199904090250.TAA40298@google.engr.sgi.com \
--to=kanoj@google.engr.sgi.com \
--cc=ebiederm+eric@ccr.net \
--cc=kmorgan@inter-tax.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.