From: Pete Zaitcev <zaitcev@redhat.com>
To: Tony.P.Lee@nokia.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: mprotect() api overhead.
Date: Fri, 5 Apr 2002 23:13:59 -0500 [thread overview]
Message-ID: <20020405231359.A25663@devserv.devel.redhat.com> (raw)
> From: <Tony.P.Lee@nokia.com>
> Date: Fri, 22 Mar 2002 22:10:20 PST
> We like to design a software in certain module way. For example,
> a libForwardTableManager.so for infiniband switch manager
> might manager 128 MBytes of share memory data. 10 or more
> applications will call the APIs in the libForwardTableManager.so
> to get/set the forward table data.
>[...]
> What I like to do is to use the mprotect() api to turn on/off the
> memory read/write access to the globally share memory. This
> way, the only possible memory corruption to the share table
> is from the APIs in the libForwardTableManager.so
Tony, I think you need to rethink your API.
E.g. what does the switch manager do and why did you
decide to keep any data in a shared memory, of all things?
Why do you need several applications to access the
switch forwarding table? Perhaps, if you answer those
questions, you do not need to bang mprotect() so hard
anymore.
-- Pete
next reply other threads:[~2002-04-06 4:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 4:13 Pete Zaitcev [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-23 1:59 mprotect() api overhead Tony.P.Lee
2002-03-23 2:20 ` Alan Cox
2002-03-25 4:19 ` Benjamin LaHaise
2002-03-22 23:09 Tony.P.Lee
2002-03-22 22:10 Tony.P.Lee
2002-03-22 22:57 ` Andrew Morton
2002-03-23 1:03 ` Alan Cox
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=20020405231359.A25663@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=Tony.P.Lee@nokia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox