From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: John Ousterhout <ouster@cs.stanford.edu>
Cc: "Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] eal: avoid unnecessary conflicts over rte_config file
Date: Thu, 13 Oct 2016 18:31:38 +0200 [thread overview]
Message-ID: <1697764.L6jCD5RFoR@xps13> (raw)
In-Reply-To: <CAGXJAmzi4jHO_yu0nPE8RCg5=6z6eC8bMGi3WYFSEB4vWyDs=A@mail.gmail.com>
2016-10-13 09:20, John Ousterhout:
> Hi Harry,
>
> But, given the existence of the --file-prefix option, isn't it already
> unsafe for Collectd to check only for .rte_config? If it's important for
> other programs to be able to find the config files, it seems to me that a
> more robust mechanism is needed than the current one.
+1
And the default location of the file should respect the Linux standards,
e.g. .config/dpdk/...
next prev parent reply other threads:[~2016-10-13 16:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 21:29 John Ousterhout
2016-10-13 10:53 ` Ananyev, Konstantin
2016-10-13 15:42 ` John Ousterhout
2016-10-13 16:07 ` Van Haaren, Harry
2016-10-13 16:20 ` John Ousterhout
2016-10-13 16:30 ` Van Haaren, Harry
2016-10-13 18:28 ` Stephen Hemminger
2016-10-13 16:31 ` Thomas Monjalon [this message]
2016-10-13 17:01 ` Ananyev, Konstantin
2016-10-13 21:39 ` Tahhan, Maryam
2016-10-14 16:27 ` John Ousterhout
2019-01-11 21:52 ` Ferruh Yigit
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=1697764.L6jCD5RFoR@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=ouster@cs.stanford.edu \
/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).