From: "Wiles, Keith" <keith.wiles@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: cuyu tang <me@expoli.tech>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: Pktgen failing in a virtualbox virtual machine
Date: Sun, 3 Nov 2024 16:34:28 +0000 [thread overview]
Message-ID: <DM6PR11MB4593EC5EFB0A4E41C38275D9FE502@DM6PR11MB4593.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241103075343.58e0dcd6@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1421 bytes --]
> Pktgen no longer has a maintainer, so it considered abandoned at this point.
> What does DPDK startup show? The problem is probably that virtualbox doesn't fully
> emulate the Intel NIC and the DPDK PMD doesn't like that.
>
> Hi Stephen,
> (sorry if formatting is bad as MacOS Outlook has some issues with plain text replies)
>
> I still maintain Pktgen, but mostly from GitHub issues @ https://github.com/pktgen/Pktgen-DPDK I do have very limited time, so not always the fastest responses.
> DPDK gets a lot of emails and sometimes I miss these emails (need to improve my emails rule filter).
> I do update dpdk.org Pktgen repo when I can, but it seemed like most of the requests were coming from GitHub.
>
> This person created an issue at Pktgen GitHub and also posted to this group at the same time. I did respond to his issue and try to work out a solution. I never test using a VM or containers, so it is difficult to help them sometimes.
>
> If you wish you can remove Pktgen from dpdk.org, but if you do please include a link to the GitHub repository.
> Thank you.
>
>
That's great. I assumed (always bad to do) that since there was hardly any activity in dpdk.org repo
that you were off doing other things. Which place do you want to keep as primary repo?
I would like to keep the primary repo @ https://github.com/pktgen/Pktgen-DPDK and use issues to track questions and requests.
[-- Attachment #2: Type: text/html, Size: 3360 bytes --]
next prev parent reply other threads:[~2024-11-03 16:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-31 9:57 cuyu tang
2024-11-02 16:03 ` Stephen Hemminger
2024-11-03 15:36 ` Wiles, Keith
2024-11-03 15:53 ` Stephen Hemminger
2024-11-03 16:34 ` Wiles, Keith [this message]
2024-11-01 1:18 cuyu tang
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=DM6PR11MB4593EC5EFB0A4E41C38275D9FE502@DM6PR11MB4593.namprd11.prod.outlook.com \
--to=keith.wiles@intel.com \
--cc=me@expoli.tech \
--cc=stephen@networkplumber.org \
--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).