All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 215] IPC socket of 2 primary processes may conflict
Date: Tue, 26 Feb 2019 16:19:15 +0000	[thread overview]
Message-ID: <bug-215-3-5GBsial01g@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-215-3@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=215

Anatoly Burakov (anatoly.burakov@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Anatoly Burakov (anatoly.burakov@intel.com) ---
This is incorrect. Socket path is generated from create_socket_path() call at
eal_common_proc.c:135. That, in turn, will call eal_mp_socket_path(), which
uses rte_eal_get_runtime_dir() to get its path. That path includes the hugefile
prefix.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2019-02-26 16:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-26 16:14 [Bug 215] IPC socket of 2 primary processes may conflict bugzilla
2019-02-26 16:19 ` bugzilla [this message]

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=bug-215-3-5GBsial01g@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.