DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Ray Kinsella <mdr@ashroe.eu>
Cc: "Halim, Abdul" <abdul.halim@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v5] build: add dockerfile for building docker image
Date: Sun, 11 Jun 2023 19:44:10 -0700	[thread overview]
Message-ID: <20230611194410.300d999b@hermes.local> (raw)
In-Reply-To: <8b3accf7-4e24-4874-15ee-3f840c0f08e5@ashroe.eu>

On Wed, 11 Dec 2019 17:00:14 +0000
Ray Kinsella <mdr@ashroe.eu> wrote:

> > 
> > Hi Ray,
> > Our intent here is to show how to use this dpdk shared lib in container to build 
> > an application and run it. The same steps can be taken for any other advanced 
> > DPDK apps to take advantage of this shared library.
> > As you've mentioned, other apps will require various  HW related configuration 
> > to be shown and explained. The DPDK documentation already cover them 
> > in details. And that may unintentionally divert the focus to that particular app.
> > This is my opinion only :) 
> > 
> > However, if you strongly feel that the example should be with one of the apps
> > you've mentioned I can update it accordingly.
> > 
> > Many thanks!
> > 
> > Regards,
> > Abdul  
> 
> My simple point is that DPDK without a network card, is not the majority use case.
> Dataplane Development Kit implies some sort of a network data plane :-)
> 
> Thanks, 
> 
> Ray K

Have to agree with Ray here. The DPDK build process is complex and robust enough
as is. Unless someone wants to go farther with container based build, it doesn't
look like this patch got any traction in 4 years so dropping it.

  reply	other threads:[~2023-06-12  2:44 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-27 16:44 [dpdk-dev] [PATCH] " Abdul Halim
2019-09-30  8:54 ` Ray Kinsella
2019-09-30 12:21   ` Halim, Abdul
2019-10-04 10:08 ` [dpdk-dev] [PATCH v2] " Abdul Halim
2019-10-15  8:39   ` Ray Kinsella
2019-11-13 20:26     ` Yasufumi Ogawa
2019-12-03 11:42 ` [dpdk-dev] [PATCH v3] " Abdul Halim
2019-12-05 14:13   ` Ruifeng Wang (Arm Technology China)
2019-12-05 19:51     ` Yasufumi Ogawa
2019-12-06 11:12       ` Halim, Abdul
2019-12-09  3:23         ` Ruifeng Wang (Arm Technology China)
2019-12-09  9:44           ` Yasufumi Ogawa
2019-12-09 10:18         ` Yasufumi Ogawa
2019-12-10 13:16           ` Halim, Abdul
2019-12-10 13:44 ` [dpdk-dev] [PATCH v4] " Abdul Halim
2019-12-10 13:55 ` [dpdk-dev] [PATCH v5] " Abdul Halim
2019-12-10 17:44   ` Ray Kinsella
2019-12-11 10:53     ` Halim, Abdul
2019-12-11 17:00       ` Ray Kinsella
2023-06-12  2:44         ` Stephen Hemminger [this message]
2019-12-11  6:45   ` Ruifeng Wang (Arm Technology China)
2019-12-11 16:35     ` Halim, Abdul
2019-12-11 16:39 ` [dpdk-dev] [PATCH v6] " Abdul Halim
2019-12-12  6:53   ` Ruifeng Wang (Arm Technology China)

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=20230611194410.300d999b@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=abdul.halim@intel.com \
    --cc=dev@dpdk.org \
    --cc=mdr@ashroe.eu \
    /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).