From: Thomas Monjalon <thomas@monjalon.net>
To: Bruce Richardson <bruce.richardson@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Anatoly Burakov <anatoly.burakov@intel.com>,
dev@dpdk.org, Kevin Laatz <kevin.laatz@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/ring: support secondary process
Date: Sun, 07 Mar 2021 22:02:57 +0100 [thread overview]
Message-ID: <1830255.sq908RcW1U@thomas> (raw)
In-Reply-To: <afaadbe5-36f9-cb52-e99b-6d6f43cf1640@intel.com>
04/03/2021 18:14, Ferruh Yigit:
> On 3/1/2021 1:38 PM, Bruce Richardson wrote:
> > On Wed, Sep 30, 2020 at 12:02:40PM +0100, Ferruh Yigit wrote:
> >> Also add missing .ini feature list documentation and document some
> >> existing features including new "Multiprocess aware" feature.
> >>
> >> Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> >> ---
> >> Cc: Kevin Laatz <kevin.laatz@intel.com>
> >> ---
> >> doc/guides/nics/features/ring.ini | 10 ++++++++++
> >> drivers/net/ring/rte_eth_ring.c | 17 +++++++++++++++++
> >> 2 files changed, 27 insertions(+)
> >> create mode 100644 doc/guides/nics/features/ring.ini
> >>
> > Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> >
>
> Applied to dpdk-next-net/main, thanks.
Sorry, just seeing now.
I think we should not re-introduce the ring PMD in the features table.
It is not significant enough to occupy a column in this table I think.
This is the commit where I removed it from the table:
https://git.dpdk.org/dpdk/commit/?id=7b103c4ccd
next prev parent reply other threads:[~2021-03-07 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 11:02 [dpdk-dev] [PATCH] net/ring: support secondary process Ferruh Yigit
2021-02-17 17:49 ` Ferruh Yigit
2021-03-01 13:38 ` Bruce Richardson
2021-03-04 17:14 ` Ferruh Yigit
2021-03-07 21:02 ` Thomas Monjalon [this message]
2021-03-08 11:30 ` Ferruh Yigit
2021-03-08 11:39 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-03-09 8:40 ` Ferruh Yigit
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=1830255.sq908RcW1U@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kevin.laatz@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.