Bug #91329 for File-Map: File::Map and RAM disks.

Wed Dec 11 15:27:52 2013 andrewksmith [...] gmail.com - Ticket created

Subject:	File::Map and RAM disks.
Date:	Wed, 11 Dec 2013 15:27:42 -0500
To:	bug-File-Map [...] rt.cpan.org
From:	Andrew Smith <andrewksmith [...] gmail.com>

Hi, I've been using your module File::Map and it has been working well, but I had a question and possible feature request. How would File::Map deal with the case of a file to be mapped (using map_file) that is stored on a RAM disk? On the surface this might seem funny --- if you have a RAM disk why would you need to use File::Map, just use the RAM disk directly. But it might still be nice to access the RAM disk via File::Map (i.e. same interface no matter how/where the file is stored). So how would File::Map handle this situation? Would it just remap the file again in memory, or is it smart enough to know it is accessing a RAM disk and thus wouldn't remap? If it doesn't know about RAM disks it might be nice to add this feature in --- e.g. allow the user to specify that the file to be mapped is stored in a RAM disk and then don't have File::Map map it into memory again. thanks, Andrew Smith

Wed Jan 08 11:06:58 2014 LEONT [...] cpan.org - Correspondence added

Subject:	Re: [rt.cpan.org #91329] File::Map and RAM disks.
Date:	Wed, 8 Jan 2014 17:06:30 +0100
To:	bug-File-Map [...] rt.cpan.org
From:	Leon Timmermans <leont [...] cpan.org>

On Wed, Dec 11, 2013 at 9:27 PM, Andrew Smith via RT < bug-File-Map@rt.cpan.org> wrote: Show quoted text

> Hi, > > I've been using your module File::Map and it has been working well, but I > had a question and possible feature request. How would File::Map deal with > the case of a file to be mapped (using map_file) that is stored on a RAM > disk? On the surface this might seem funny --- if you have a RAM disk why > would you need to use File::Map, just use the RAM disk directly. But it > might still be nice to access the RAM disk via File::Map (i.e. same > interface no matter how/where the file is stored). So how would File::Map > handle this situation? Would it just remap the file again in memory, or is > it smart enough to know it is accessing a RAM disk and thus wouldn't remap? > If it doesn't know about RAM disks it might be nice to add this feature in > --- e.g. allow the user to specify that the file to be mapped is stored in > a RAM disk and then don't have File::Map map it into memory again. > >

Your operating system takes care of all of that, look up virtual memory system if you're interested in how this works. :-) Leon

Wed Jan 08 11:06:59 2014 The RT System itself - Status changed from 'new' to 'open'

Fri Jan 17 08:58:31 2014 LEONT [...] cpan.org - Status changed from 'open' to 'resolved'