DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: John Bize <john.bize@cantada.com>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: USB device support in DPDK
Date: Mon, 5 Dec 2022 08:01:33 -0800	[thread overview]
Message-ID: <20221205080133.28dc4080@hermes.local> (raw)
In-Reply-To: <2324603.NG923GbCHz@thomas>

On Mon, 05 Dec 2022 10:07:44 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:

> 02/12/2022 14:01, John Bize:
> > Will DPDK support USB-Ethernet devices?  
> 
> If there is a need and an advantage for USB devices
> to be supported in DPDK, why not?
> 
> In general, DPDK supports what is contributed and maintained.
> 
> 

One recent Linux kernel thread was about removing all the RNDIS
USB devices because there are fundamental security problems with
the protocol.

  reply	other threads:[~2022-12-05 16:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 13:01 John Bize
2022-12-05  9:07 ` Thomas Monjalon
2022-12-05 16:01   ` Stephen Hemminger [this message]
2022-12-05 16:00 ` 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=20221205080133.28dc4080@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=john.bize@cantada.com \
    --cc=thomas@monjalon.net \
    --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).