From: Tanvir Kekan <tanvir.kekan@gmail.com>
To: Adel Belkhiri <adel.belkhiri@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] Exporting DPDK network interfaces statistics
Date: Sun, 22 Mar 2020 01:02:17 -0700 [thread overview]
Message-ID: <CAJLP_YBz_E5ixyJyRsrjvUm2wBCWoCAq-W=bOv66EXUFmYRqdQ@mail.gmail.com> (raw)
In-Reply-To: <CAMxxxdP3_FkNpi-c9Eq4z7B_1w9FcsvttVo_XMaH1OX4zBcH1A@mail.gmail.com>
Have you looked at mirroring the traffic
Of each interface to different vf ?
Thanks
Tanvir K
On Sat, Mar 21, 2020 at 11:47 AM Adel Belkhiri <adel.belkhiri@gmail.com>
wrote:
> Hello guys,
>
> I'm trying to develop a monitoring tool capable of exporting some
> statistics about DPDK network interfaces. The problem with spawning a
> "secondary process", the way proc-info does, is that not all the network
> interfaces are "seen" but just those managed by a single primary process.
>
> I was wondering if there is another way to implement this without spawning
> many processes.
>
> Thank you.
>
> Adel.
>
next prev parent reply other threads:[~2020-03-22 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 18:47 Adel Belkhiri
2020-03-22 8:02 ` Tanvir Kekan [this message]
2020-03-23 11:31 ` Bruce Richardson
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='CAJLP_YBz_E5ixyJyRsrjvUm2wBCWoCAq-W=bOv66EXUFmYRqdQ@mail.gmail.com' \
--to=tanvir.kekan@gmail.com \
--cc=adel.belkhiri@gmail.com \
--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 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).