mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Elson <jelson@circlemud.org>
To: linux-kernel@vger.kernel.org
Cc: jelson@circlemud.org
Subject: Mapping a piece of one process' addrspace to another?
Date: Tue, 06 Mar 2001 21:19:28 -0800	[thread overview]
Message-ID: <200103070519.f275JSw05855@servo.isi.edu> (raw)

Greetings,

Is there some way to map a piece of process X's address space into
process Y, without X's knowledge or cooperation?  (The non-cooperating
nature of process X is why I can't use plain old shared memory.)

Put another way, I need to grant Process Y permission to write into a
private buffer owned by process X.  X doesn't know this is happening,
and I don't know where X's buffer even lives (X's stack, heap, etc.).
X just passes a pointer to the kernel via a system call (e.g., like
sys_read).

In the system I currently have implemented, Y writes a buffer to the
kernel, and the kernel relays it to X on behalf of Y.  But, for
performance reasons, I want to try to get Y to write its data directly
to X instead.  X might be any process calling read() (e.g., "cat"),
but Y is in collusion with the kernel.

If this is possible at all, is it also possible on a granularity down
to one byte (as opposed to an entire page)?

Sorry if this seems like a strange thing to do - but, I hope to
document and release my code soon, in which case its purpose should be
clearer :-).

Regards,
Jeremy

             reply	other threads:[~2001-03-07  5:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-07  5:19 Jeremy Elson [this message]
2001-03-07  5:55 ` Alexander Viro
2001-03-07  6:02   ` Marcelo Tosatti
2001-03-07  8:13     ` Jeremy Elson
2001-03-07  8:40       ` Alexander Viro
2001-03-07  8:54         ` Jeremy Elson
2001-03-07  9:09           ` Alexander Viro
2001-03-07 23:22             ` James H. Cloos Jr.
2001-03-07  9:04         ` Abramo Bagnara
2001-03-07  9:10           ` Alexander Viro
2001-03-07  9:20             ` Abramo Bagnara
2001-03-07  9:49               ` Alexander Viro
2001-03-07 13:01                 ` Abramo Bagnara
2001-03-07 21:02                 ` Jeremy Elson
2001-03-07  8:58       ` Abramo Bagnara
2001-03-07 18:17     ` Pavel Machek
2001-03-07 10:51 Manfred Spraul
2001-03-07 13:57 Jesse Pollard

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=200103070519.f275JSw05855@servo.isi.edu \
    --to=jelson@circlemud.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®