>
>
> On Thu, 30 Jul 1998, Benjamin C.R. LaHaise wrote:
> >
> > (a) sounds like the Obvious Thing To Do in the mmap method for /proc, but
> > will break xdos. Wtf were they thinking in writing that insane code?
> > Hmmm, this bug probably applies to 2.0 too.... in a much more subtle
> > fashion.
>
> The insane code is indeed insane, but I think I understand why they did
> it: they didn't want to mess around with sysv shared memory regions.
Good guess but no. Dosemu already uses sysv shared memory regions
where it can. But for some applications it needs page level control,
and sysv doesn't give you that.
Further the dosemu history states that when it was attempted to map a
temporary file, and use the standard mmap functionality that way, the
performance became unacceptable on nfs filesystems.
So /proc/self/mem was the only solution open to dosemu, that provided
the required level of performance and control.
> I'd love to just completely get rid of mmap() on /proc/self/mem, because
> it actually is a bad idea completely (not just the shared mappings - even
> a private mapping of another mapping that is shared has simply completely
> untenable logical problems).
I agree and this is why I have put a considerable amount of effort into
implementing a posix shared memory interface.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.altern.org/andrebalsa/doc/lkml-faq.html