From: Thanos Makatos <thanos.makatos@nutanix.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] question about implication of --no-shconf on sharing file descriptors
Date: Tue, 23 Mar 2021 16:50:59 +0000 [thread overview]
Message-ID: <MW2PR02MB3723435869FF35E02D2A150E8B649@MW2PR02MB3723.namprd02.prod.outlook.com> (raw)
I'm looking at using the --in-memory option and from what I see it implies the --no-shconf option.
IIUC this memory will not be backed by a file, so there won't be file descriptor to pass to another process, right?
reply other threads:[~2021-03-23 16:51 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=MW2PR02MB3723435869FF35E02D2A150E8B649@MW2PR02MB3723.namprd02.prod.outlook.com \
--to=thanos.makatos@nutanix.com \
--cc=users@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).