From: Shahaf Shuler <shahafs@mellanox.com>
To: "Yongseok Koh" <yskoh@mellanox.com>,
"Adrien Mazarguil" <adrien.mazarguil@6wind.com>,
"Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"hhaim@cisco.com" <hhaim@cisco.com>,
Yongseok Koh <yskoh@mellanox.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 1/2] net/mlx5: fix Memory Region registration
Date: Thu, 21 Dec 2017 15:26:10 +0000 [thread overview]
Message-ID: <VI1PR05MB3149F042E48C4DEDB9A726D2C30D0@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20171215015918.30981-1-yskoh@mellanox.com>
Friday, December 15, 2017 3:59 AM, Yongseok Koh:
> Althought granularity of chunks in a mempool is a cacheline, addresses are
> extended to align to page boundary for performance reason in device when
> registering a MR (Memory Region). This could make some regions overlap,
> then can cause Tx completion error due to incorrect LKEY search. If the error
> occurs, the Tx queue will get stuck. To avoid it, end address of a packet
> segment is used in LKEY search.
>
> Fixes: b0b093845793 ("net/mlx5: use buffer address for LKEY search")
> Cc: stable@dpdk.org
>
> Reported-by: Hanoch Haim <hhaim@cisco.com>
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Series applied to next-net-mlx, thanks.
prev parent reply other threads:[~2017-12-21 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 1:59 Yongseok Koh
2017-12-15 1:59 ` [dpdk-stable] [PATCH 2/2] net/mlx5: fix overflow of Memory Region cache Yongseok Koh
2017-12-21 15:26 ` Shahaf Shuler [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=VI1PR05MB3149F042E48C4DEDB9A726D2C30D0@VI1PR05MB3149.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=adrien.mazarguil@6wind.com \
--cc=dev@dpdk.org \
--cc=hhaim@cisco.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=stable@dpdk.org \
--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 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).