From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, olivier.matz@6wind.com, yskoh@mellanox.com,
arybchenko@solarflare.com, bernard.iremonger@intel.com
Subject: Re: [PATCH v2 0/3] segment sanity checks
Date: Tue, 15 Jan 2019 02:33:04 +0100 [thread overview]
Message-ID: <2396925.LEeXtTcc9E@xps> (raw)
In-Reply-To: <1546851432-19397-1-git-send-email-david.marchand@redhat.com>
07/01/2019 09:57, David Marchand:
> Resubmitting this series that I did not finish in my previous life (6WIND
> people are okay with this).
>
> Here is a little series which helped me identify a multi segment issue.
> Hope it can help others.
>
> The difference since the RFC patches I sent some time ago is that, rather
> than force the user to build the dpdk with CONFIG_RTE_LIBRTE_MBUF_DEBUG
> enabled, it uses rx/tx callbacks to apply checks on the mbufs.
>
> Changelog since v1:
> - dropped unnecessary casts in patch 1,
> - rewrote patch 3: reused the existing rx/tx callbacks and left the invalid
> mbufs in rx bulk
Applied, thanks
prev parent reply other threads:[~2019-01-15 1:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 8:57 [PATCH v2 0/3] segment sanity checks David Marchand
2019-01-07 8:57 ` [PATCH v2 1/3] mbuf: add sanity checks on segment metadata David Marchand
2019-01-07 8:57 ` [PATCH v2 2/3] mbuf: add a non fatal sanity check helper David Marchand
2019-01-07 8:57 ` [PATCH v2 3/3] app/testpmd: check mbufs in verbose mode David Marchand
2019-01-08 9:53 ` Iremonger, Bernard
2019-01-15 1:33 ` Thomas Monjalon [this message]
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=2396925.LEeXtTcc9E@xps \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=bernard.iremonger@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=yskoh@mellanox.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.