From: David Marchand <david.marchand@6wind.com>
To: dev@dpdk.org
Cc: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [RFC 2/2] ethdev: check received mbufs sanity
Date: Fri, 24 Aug 2018 12:17:31 +0200 [thread overview]
Message-ID: <CALwxeUu7L3MuxyKZRRcdfS7vcFqQ7AhqDXGgUXQ4vgME5Gr-Cw@mail.gmail.com> (raw)
In-Reply-To: <1534176226-21911-2-git-send-email-david.marchand@6wind.com>
On Mon, Aug 13, 2018 at 6:03 PM, David Marchand
<david.marchand@6wind.com> wrote:
> Let's check the mbufs given by the drivers directly in the rx handler.
> The only drawback is that you need CONFIG_RTE_LIBRTE_MBUF_DEBUG to be set
> for this to actually do some real checks.
Comments ?
--
David Marchand
next prev parent reply other threads:[~2018-08-24 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 16:03 [dpdk-dev] [RFC 1/2] mbuf: add a sanity check on segment metadata David Marchand
2018-08-13 16:03 ` [dpdk-dev] [RFC 2/2] ethdev: check received mbufs sanity David Marchand
2018-08-24 10:17 ` David Marchand [this message]
2018-08-23 7:39 ` [dpdk-dev] [RFC 1/2] mbuf: add a sanity check on segment metadata Olivier Matz
2018-08-23 7:45 ` David Marchand
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=CALwxeUu7L3MuxyKZRRcdfS7vcFqQ7AhqDXGgUXQ4vgME5Gr-Cw@mail.gmail.com \
--to=david.marchand@6wind.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=olivier.matz@6wind.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).