From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Crashes if running WordPerfect 5.1
Date: Tue, 01 Jun 2004 07:53:25 +0400 [thread overview]
Message-ID: <40BBFDB5.1030105@aknet.ru> (raw)
Hello.
Bart Oldeman wrote:
> I think I would personnally like it best if there wasn't a pagealloc
> either, but just multiple fd's.
Yes, I already recognized that as a
good idea even for mapfile (esp. now
on /dev/shm), so the first step I was
going to take, is to avoid pagemalloc
for mapfile.
> That way you can have only one mapping
> backend, it just differs in what the fd opens (i.e. /dev/zero or a
> temporary file, or perhaps shm_open), and we don't need the mremap
> trick.
Also we may not need the multiple
mapping backends amymore then, since
the only difference would be how the
fd is being opened.
> alloc_mapping opens a /dev/zero
Was it already verified that this can
be shared without mremap?
or tmpfile -- the fd will be remembered
> (linked list connecting it to the memory address)
Yes, somewhat resembling the tracking
of kmem mappings in mapping.c I think.
The problem is that the run-time check
for NPTL will not help, we need a
compile-time check if we want to use
open_shm(). That will mean the binary-
distributed dosemu will either have
open_shm() disabled, or not working
with linuxthreads. Or maybe dlopen()
librt? No fun... How's your ptrace patch
going? It could really help in resolving
this mess.
next reply other threads:[~2004-06-01 3:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-01 3:53 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-06-19 11:01 Crashes if running WordPerfect 5.1 Stas Sergeev
2004-06-01 4:25 Stas Sergeev
2004-05-31 18:06 Stas Sergeev
2004-05-30 13:41 Stas Sergeev
2004-05-31 21:06 ` Bart Oldeman
2004-05-30 0:29 Stas Sergeev
2004-05-30 10:55 ` Bart Oldeman
2004-05-30 11:40 ` Bart Oldeman
2004-05-29 18:13 Stas Sergeev
2004-05-29 20:47 ` Bart Oldeman
2004-05-31 16:41 ` Lars Bjørndal
2004-05-29 15:49 Lars Bjørndal
2004-05-29 16:28 ` Bart Oldeman
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=40BBFDB5.1030105@aknet.ru \
--to=stsp@aknet.ru \
--cc=linux-msdos@vger.kernel.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