From: Olivier MATZ <olivier.matz@6wind.com>
To: "Ilya V. Matveychikov" <matvejchikov@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] mbuf: check sanity of data_len and pkt_len as well
Date: Thu, 14 Dec 2017 09:50:25 +0100 [thread overview]
Message-ID: <20171214085024.w7mkpogcli7qp3lp@platinum> (raw)
In-Reply-To: <20171209213918.6311-1-matvejchikov@gmail.com>
On Sun, Dec 10, 2017 at 12:39:18AM +0300, Ilya V. Matveychikov wrote:
> Update rte_mbuf_sanity_check() to check sanity of data_len and pkt_len
> fields. For segmented packets it is supposed that head's pkt_len field
> should be the sum of all segments data_len values.
>
> Signed-off-by: Ilya V. Matveychikov <matvejchikov@gmail.com>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
Thanks
next prev parent reply other threads:[~2017-12-14 8:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 14:04 [dpdk-dev] [PATCH 1/2] " Ilya Matveychikov
2017-12-01 16:37 ` Olivier MATZ
2017-12-09 21:39 ` [dpdk-dev] [PATCH v2] " Ilya V. Matveychikov
2017-12-14 8:50 ` Olivier MATZ [this message]
2017-12-14 9:31 ` Olivier MATZ
2018-01-11 23:23 ` Thomas Monjalon
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=20171214085024.w7mkpogcli7qp3lp@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=matvejchikov@gmail.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 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).