public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Matt Miller <mmiller@hick.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.6: mmap complement, fdmap
Date: Mon, 22 Mar 2004 13:00:50 -0600	[thread overview]
Message-ID: <20040322190047.GC8366@waste.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0403212346330.24801@jethro.hick.org>

On Mon, Mar 22, 2004 at 12:14:56AM -0600, Matt Miller wrote:
> > On Sun, Mar 21, 2004 at 10:43:07PM -0600, Matt Miller wrote:
> > > 	``flags'' can be one of O_RDONLY, O_WRONLY, or O_RDWR.
> > >
> > > I have verified functionality on ia32 and sparc as these are the only
> > > architectures I currently have some type of access to.  To test, start the
> > > kernel configuration process and go under File systems/Pseudo filesystems
> > > and select this option:
> > >
> > > 	[*] Virtual memory file descriptor mapping support
> > >
> > > Please let me know about any and all suggestions/bugs/flames.  I tried to
> >
> > *boggle*
> >
> > a) what the hell for?
> 
> It's targetted mainly as a performance enhancer.  Some of the specific
> scenarios where it would be useful are:
> 
> a) When one cannot afford to take the performance hit of synchronizing
>    a memory range to disk due to disk size limitations or speed
>    requirements.
> b) Some things can benefit from the ability to interface with memory as a
>    file.
> 
> The specific reason for implementing this was to allow for loading dynamic
> libraries in the context of a process without having to write them to
> disk.

How about tmpfs/ramfs instead? Open a file on tmpfs and mmap it and
you've got the same thing without any of the nasty corner cases.
 
-- 
Matt Mackall : http://www.selenic.com : Linux development and consulting

  reply	other threads:[~2004-03-22 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-22  4:43 [PATCH] 2.6: mmap complement, fdmap Matt Miller
2004-03-22  5:30 ` viro
2004-03-22  6:14   ` Matt Miller
2004-03-22 19:00     ` Matt Mackall [this message]
2004-03-22 19:26       ` Matt Miller
2004-03-23  0:52         ` Matt Mackall
2004-03-23  4:26           ` Matt Miller

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=20040322190047.GC8366@waste.org \
    --to=mpm@selenic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmiller@hick.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