From: Neil Horman <nhorman@tuxdriver.com>
To: Uri Sidler <uri.sidler@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] using hash table in a MP environment
Date: Tue, 10 Jun 2014 07:35:21 -0400 [thread overview]
Message-ID: <20140610113521.GD6275@hmsreliant.think-freely.org> (raw)
In-Reply-To: <CACxZdGrb=Tq3XyJkbnXd7WCLZOYJYwGtjFBT=9-89rQVd-WOeQ@mail.gmail.com>
On Tue, Jun 10, 2014 at 11:02:03AM +0300, Uri Sidler wrote:
> Hi,
> I am currently using a hash table in a multi-process environment.
> the master process creates the hash table which is later used by other
> secondary processes.
> but the secondary processes fail to use the hash table since the hash
> function address actually points to a different fucntion. (this makes sense
> since the address of the hash function is in fact different per process).
> How can I solve this issue?
>
> Thanks,
> Shirley.
>
Use shared memory. see shmget
Neil
next prev parent reply other threads:[~2014-06-10 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-10 8:02 Uri Sidler
2014-06-10 11:35 ` Neil Horman [this message]
2014-06-10 12:25 ` Venkat Thummala
2014-06-11 5:23 ` Helmut Sim
2014-06-11 15:16 ` Richardson, Bruce
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=20140610113521.GD6275@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=uri.sidler@gmail.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;
as well as URLs for NNTP newsgroup(s).