From: Pallavi Kadam <pallavi.kadam@intel.com>
To: dev@dpdk.org, thomas@monjalon.net
Cc: ranjit.menon@intel.com, dmitry.kozliuk@gmail.com,
Narcisa.Vasile@microsoft.com, talshn@nvidia.com,
pallavi.kadam@intel.com
Subject: [dpdk-dev] [PATCH v2] eal: enable windows apps to run on non-admin users
Date: Mon, 26 Oct 2020 11:44:58 -0700 [thread overview]
Message-ID: <20201026184458.8492-1-pallavi.kadam@intel.com> (raw)
In-Reply-To: <20201021202616.2732-1-pallavi.kadam@intel.com>
Currently, since there is no runtime directory set, the code tries to
create a file in C:\ which is only writable with administrator
privileges. As a result, if the user is not admin, the application will
fail.
So, forcing no_shconf to 1 to prevent the code having to create files in
the runtime directory.
Suggested-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Signed-off-by: Pallavi Kadam <pallavi.kadam@intel.com>
Reviewed-by: Ranjit Menon <ranjit.menon@intel.com>
---
lib/librte_eal/windows/eal.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/librte_eal/windows/eal.c b/lib/librte_eal/windows/eal.c
index 6334aca03..105549de1 100644
--- a/lib/librte_eal/windows/eal.c
+++ b/lib/librte_eal/windows/eal.c
@@ -295,6 +295,7 @@ rte_eal_init(int argc, char **argv)
RTE_LOG(WARNING, EAL, "Multi-process support is requested, "
"but not available.\n");
internal_conf->in_memory = 1;
+ internal_conf->no_shconf = 1;
}
if (!internal_conf->no_hugetlbfs && (eal_hugepage_info_init() < 0)) {
--
2.18.0.windows.1
next prev parent reply other threads:[~2020-10-26 18:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-21 20:26 [dpdk-dev] [PATCH] eal: create a runtime directory on windows Pallavi Kadam
2020-10-22 18:15 ` Ranjit Menon
2020-10-22 19:05 ` Dmitry Kozlyuk
2020-10-26 19:01 ` Kadam, Pallavi
2020-10-26 18:44 ` Pallavi Kadam [this message]
2020-10-27 23:10 ` [dpdk-dev] [PATCH v2] eal: enable windows apps to run on non-admin users Dmitry Kozlyuk
2020-10-28 12:41 ` Burakov, Anatoly
2020-11-03 20:28 ` Thomas Monjalon
2020-10-29 18:37 ` Narcisa Ana Maria Vasile
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=20201026184458.8492-1-pallavi.kadam@intel.com \
--to=pallavi.kadam@intel.com \
--cc=Narcisa.Vasile@microsoft.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@nvidia.com \
--cc=thomas@monjalon.net \
/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).