From: "Rafael Sisto" <rafael.sisto@gmail.com>
To: "Luciano Rocha" <luciano@eurotux.com>,
"Rafael Sisto" <rafael.sisto@gmail.com>,
"Linux kernel" <linux-kernel@vger.kernel.org>
Subject: Re: shared memory
Date: Sun, 16 Dec 2007 17:01:17 -0300 [thread overview]
Message-ID: <ee3dc96c0712161201y34a3e3e0t601ab4fa73d002c@mail.gmail.com> (raw)
In-Reply-To: <20071216195715.GA10287@bit.office.eurotux.com>
Thank you for the quick answer, but It's a college project, and I must
share user level memory. I also must build my own system calls...
But I can look what is already done and make something similar. Do you
think shmget would do? Does it share user level memory?
greetings!
Rafael Sisto
On Dec 16, 2007 4:57 PM, Luciano Rocha <luciano@eurotux.com> wrote:
> On Sun, Dec 16, 2007 at 04:51:39PM -0300, Rafael Sisto wrote:
> > Hi, Im working on a project working on linux kernel 2.6.17
> > I have to share memory on user level... I have to build something like
> > a server process that "exports" a portion of his virtual memory, and
> > other client process may ask the kernel for that memory and use it (as
> > its own).
> > I managed to build a structure on the kernel.
>
> Why? Aren't SysV IPC or Posix IPC enough?
>
> See "man shm_open", for the new Posix version, and "man shmget" for the
> old SysV IPC version.
>
> --
> Luciano Rocha <luciano@eurotux.com>
> Eurotux Informática, S.A. <http://www.eurotux.com/>
>
next prev parent reply other threads:[~2007-12-16 20:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-16 19:51 Rafael Sisto
2007-12-16 19:57 ` Luciano Rocha
2007-12-16 20:01 ` Rafael Sisto [this message]
2007-12-16 22:30 ` Luciano Rocha
2007-12-16 23:52 ` Rafael Sisto
-- strict thread matches above, loose matches on Subject: below --
2005-03-10 20:39 Shared memory Bloch, Jack
2001-11-20 3:57 shared memory Lee Chin
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=ee3dc96c0712161201y34a3e3e0t601ab4fa73d002c@mail.gmail.com \
--to=rafael.sisto@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luciano@eurotux.com \
/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®