From: 张伟 <zhangwqh@126.com>
To: dev@dpdk.org
Subject: [dpdk-dev] share a table
Date: Sun, 13 Mar 2016 10:55:16 +0800 (CST) [thread overview]
Message-ID: <17537df8.10d9.1536de63540.Coremail.zhangwqh@126.com> (raw)
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GBK, Size: 941 bytes --]
Hi all,
Now I use the DPDK multiple process example : client -server. I want the server create a hash table, then share it to client. Currently what I do is to create_hash_table function returns a pointer which points to the flow table (inside the create_hash_table function, I use rte_calloc function allocates the space for the flow table and entries). I use memzone stores the table address, then client maps the memzone can find the table address. But this method does not work. When I access the flow table, it will have a segment fault problem. Does anybody know what will be a good way which can allow the server create a hash table share to the client? Any suggestion will be appreciated. \x16º&¶\x1a&jɨ6¥¢~°w\¢d®Æ«×}uÓöÛMzEën®sÚ¶^[a¢f¬ãjZ'ë\b§uÊ&Eç\x1e÷~º&¨¥Âm\x1fçx(¢ ^r¦j)pGùÞ
(W¢nø×n|ÛÛÉÚ]à>-~,pØDHÄÏÞ»\x03®7×Þ_¢·^½Ú]àJéõÜÆ«ÛMz×]9ßo´×M\x02\x114^qè¯yÖò¨¥Âm\x1fçx(¢ ^r°ØR13âv}|êÊ;ÓÏw÷p}_¢·^½Ú]àJéõÜÆ«ÛMzÓ}9ßm;ÓCÃL21( «në
reply other threads:[~2016-03-13 2:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=17537df8.10d9.1536de63540.Coremail.zhangwqh@126.com \
--to=zhangwqh@126.com \
--cc=dev@dpdk.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;
as well as URLs for NNTP newsgroup(s).