DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Isaac Boukris <iboukris@gmail.com>
Cc: users@dpdk.org
Subject: Re: Multi-process limitations when using the dumpcap tool
Date: Fri, 3 Mar 2023 14:18:23 -0800	[thread overview]
Message-ID: <20230303141823.09bf1563@hermes.local> (raw)
In-Reply-To: <CAC-fF8Rv+KaYs56fDrsmogUw57izc3AqXKnYDA-H3CLR-T=S8w@mail.gmail.com>

On Fri, 3 Mar 2023 12:33:20 +0200
Isaac Boukris <iboukris@gmail.com> wrote:

> Hello,
> 
> The dumpcap documentation points out that it runs as a secondary process,
> as such I was wondering whether the multi-process limitations such as the
> requirement to disable ASLR on both processes, and more importantly the
> limitations regarding the use of librte_hash, also apply when using the
> dumpcap tool?
> 
> Thanks!

Dumpcap is passive and have not heard of any problems related to ASLR.

  reply	other threads:[~2023-03-03 22:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-03 10:33 Isaac Boukris
2023-03-03 22:18 ` Stephen Hemminger [this message]
2023-03-03 22:37   ` Isaac Boukris
2023-03-04  0:07     ` Stephen Hemminger

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=20230303141823.09bf1563@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=iboukris@gmail.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).