DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: thomas@monjalon.net
Cc: dev@dpdk.org, keith.wiles@intel.com
Subject: Re: [PATCH v4] dfs:add FUSE based filesystem for DPDK
Date: Fri,  9 Jun 2023 10:04:52 -0700	[thread overview]
Message-ID: <20230609170452.82883-1-stephen@networkplumber.org> (raw)
In-Reply-To: <2437900.lBdCot2IvA@xps>

This patch proposed an interesting extension to DPDK, but never
got any positive reviews. It creates new API's which introduces
likelihood of new bugs; and overlaps existing functionality.

Therefore recommend that it be marked rejected.

  parent reply	other threads:[~2023-06-09 17:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-16 17:46 [dpdk-dev] [PATCH v3 1/3] " Keith Wiles
2018-12-16 22:22 ` Luca Boccassi
2018-12-17 16:26   ` Wiles, Keith
2018-12-17 19:02     ` Luca Boccassi
2018-12-17 11:45 ` Thomas Monjalon
2018-12-17 15:01   ` Wiles, Keith
2018-12-17 16:12     ` Thomas Monjalon
2018-12-19 17:38     ` Wiles, Keith
2023-06-09 17:04   ` Stephen Hemminger [this message]
2018-12-27 18:16 ` [dpdk-dev] [PATCH v4] " Keith Wiles

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=20230609170452.82883-1-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=keith.wiles@intel.com \
    --cc=thomas@monjalon.net \
    /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).