The following minor changes are being made to this case material to
capture the comments received so far. An updated man page has been
added to the materials directory.
i. change name from mmapfd(2) to mmapobj(2).
ii.change data structure name, and associated flags to follow
To elaborate on this: part of the idea behind mmapfd() is that it
gives the kernel the flexibility to make global-scope decisions about
where and how a file should be mapped. [...]
The problem is that (at least in the B72 installation on the Oct 2007
Summit's T2000 machine) the auto-MPSS
On Sun, 2008-04-06 at 03:59 +0200, Roland Mainz wrote:
Michael Corcoran wrote:
On Mon, 2008-03-31 at 13:37 +0200, Roland Mainz wrote:
Rod Evans wrote:
I'm sponsoring the following case for Mike Corcoran. Time out 04/07/08.
The case introduces a new system call, mmapfd(2). This
Michael Corcoran wrote:
On Mon, 2008-03-31 at 13:37 +0200, Roland Mainz wrote:
Rod Evans wrote:
I'm sponsoring the following case for Mike Corcoran. Time out 04/07/08.
The case introduces a new system call, mmapfd(2). This call is primarily
targeted for use by ld.so.1(1), and
Blake Jones wrote:
[snip]
To elaborate on this: part of the idea behind mmapfd() is that it gives
the kernel the flexibility to make global-scope decisions about where
and how a file should be mapped. This includes the appropriate page
size to use (which might vary depending on what platform
Edward Pilatowicz wrote:
On Mon, Mar 31, 2008 at 11:46:34AM -0700, Michael Corcoran wrote:
On Mon, 2008-03-31 at 10:30 +0100, Darren J Moffat wrote:
I find the function name a bit strange. So strange in fact it made me
look at the mmap(2) man page to check that it wasn't taking a char*
Nicolas Williams wrote:
On Mon, Mar 31, 2008 at 01:37:42PM +0200, Roland Mainz wrote:
Rod Evans wrote:
mmapfd(int fd, uint_t flags, mmapfd_result_t *storage,
uint_t *elements, void *arg)
Uhm... how do I unmap the mapping done by |mmapfd()| ?
I thought that was clear (each
At today's PSARC meeting, it was asked to extend the timer to 9Apr.
As the case owner was present, I volunteered and have done so.
Gary..
I find the function name a bit strange. So strange in fact it made me
look at the mmap(2) man page to check that it wasn't taking a char*
rather than an int for the file since I was sure it took and fd. Since
mmap(2) already takes an fd.
The mmap(2) versus mmapfd(2) makes me think of
Rod Evans wrote:
I'm sponsoring the following case for Mike Corcoran. Time out 04/07/08.
The case introduces a new system call, mmapfd(2). This call is primarily
targeted for use by ld.so.1(1), and provides for the efficient mapping of
ELF files (and 4.x AOUT files).
Release Binding:
On Mon, Mar 31, 2008 at 01:37:42PM +0200, Roland Mainz wrote:
Rod Evans wrote:
mmapfd(int fd, uint_t flags, mmapfd_result_t *storage,
uint_t *elements, void *arg)
Uhm... how do I unmap the mapping done by |mmapfd()| ?
I thought that was clear (each mmapfd_result_t's mr_addr can
On Mon, 2008-03-31 at 10:30 +0100, Darren J Moffat wrote:
I find the function name a bit strange. So strange in fact it made me
look at the mmap(2) man page to check that it wasn't taking a char*
rather than an int for the file since I was sure it took and fd. Since
mmap(2) already takes
On Mon, Mar 31, 2008 at 11:46:34AM -0700, Michael Corcoran wrote:
On Mon, 2008-03-31 at 10:30 +0100, Darren J Moffat wrote:
I find the function name a bit strange. So strange in fact it made me
look at the mmap(2) man page to check that it wasn't taking a char*
rather than an int for the
On Mon, 2008-03-31 at 13:37 +0200, Roland Mainz wrote:
Rod Evans wrote:
I'm sponsoring the following case for Mike Corcoran. Time out 04/07/08.
The case introduces a new system call, mmapfd(2). This call is primarily
targeted for use by ld.so.1(1), and provides for the efficient
Michael Corcoran writes:
... what renaming the call to |mmapexecfd()| (= memory map of
executable fd) ?
I like Darren's suggestion of mmapv(2) better so far. Why limit us to
only being able to interpret executable files? What if there's some
other non-executable file type that would
On Mon, 2008-03-31 at 10:30 -0500, Nicolas Williams wrote:
On Mon, Mar 31, 2008 at 01:37:42PM +0200, Roland Mainz wrote:
Rod Evans wrote:
mmapfd(int fd, uint_t flags, mmapfd_result_t *storage,
uint_t *elements, void *arg)
Uhm... how do I unmap the mapping done by |mmapfd()|
16 matches
Mail list logo
