From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Elad Persiko <eladpe@mellanox.com>
Cc: dev@dpdk.org, Adrien Mazarguil <adrien.mazarguil@6wind.com>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: fix wrong use of vector instruction
Date: Mon, 07 Nov 2016 18:16:49 +0100 [thread overview]
Message-ID: <3453436.dEGAPM7GmK@xps13> (raw)
In-Reply-To: <20161102155602.GF5733@6wind.com>
2016-11-02 16:56, Adrien Mazarguil:
> On Tue, Nov 01, 2016 at 08:13:27AM +0000, Elad Persiko wrote:
> > Constraint alignment was not respected in Tx.
> >
> > Fixes: 1d88ba171942 ("net/mlx5: refactor Tx data path")
> >
> > Signed-off-by: Elad Persiko <eladpe@mellanox.com>
>
> Acked-by: Adrien Mazarguil <adrien.mazarguil@6wind.com>
"wrong use of vector instruction" is the cause, not the issue.
Reworded: "fix buffer alignment in Tx"
It would have been valuable to describe the consequences.
Applied
prev parent reply other threads:[~2016-11-07 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-01 8:13 Elad Persiko
2016-11-01 14:24 ` Ferruh Yigit
2016-11-02 15:56 ` Adrien Mazarguil
2016-11-07 17:16 ` 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=3453436.dEGAPM7GmK@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=eladpe@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 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).