From: David Howells <dhowells@redhat.com>
To: Christoph Rohland <cr@sap.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH,preliminary] cleanup shm handling
Date: Fri, 08 Dec 2000 15:13:45 +0000 [thread overview]
Message-ID: <20295.976288425@warthog.cygnus> (raw)
In-Reply-To: Your message of "08 Dec 2000 14:23:06 +0100." <qwwu28fkpxh.fsf@sap.com>
> here is my first shot for cleaning up the shm handling. It did survive
> some basic testing but is not ready for inclusion.
Can you help me with an SHM related problem?
I'm currently writing a Win32 emulation kernel module to help speed Wine up,
and I'm writing the file mapping support stuff at the moment
(CreateFileMapping and MapViewOfFile).
I have PE Image mapping just about working (fixups, misaligned file sections
and all), but I'm trying to think of a good way of doing anonymous shared
mappings without having to hack the main kernel around too much (so far I've
only had to add to kernel/ksyms.c).
Is there a reasonable way I could hook into the SHM system to "reserve" a
chunk of shared memory of a particular size, and then a second hook by which I
can "map" _part_ of that into a process's address space?
Cheers,
David
PS: to anyone else reading this, if you wrote do_generic_file_read(), it
rocks!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-08 15:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-08 13:23 [PATCH,preliminary] cleanup shm handling Christoph Rohland
2000-12-08 15:13 ` David Howells [this message]
2000-12-08 20:04 ` Christoph Rohland
2000-12-13 11:51 ` David Howells
2000-12-13 13:52 ` Christoph Rohland
2000-12-13 16:43 ` David Howells
2000-12-13 17:15 ` Christoph Rohland
2000-12-13 17:29 ` David Howells
2000-12-08 18:26 ` Linus Torvalds
2000-12-08 22:21 ` Christoph Rohland
2000-12-08 22:36 ` Linus Torvalds
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=20295.976288425@warthog.cygnus \
--to=dhowells@redhat.com \
--cc=cr@sap.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.