patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>,
	"Damjan Marion (damarion)" <damarion@cisco.com>,
	Ed Warnicke <hagbard@gmail.com>
Subject: Re: [dpdk-stable] [PATCH 1/2] net/mlx4: support externally allocated static memory
Date: Sun, 7 Oct 2018 11:00:38 +0000	[thread overview]
Message-ID: <DB7PR05MB4426105A3BB0CA0A0744AC0DC3E50@DB7PR05MB4426.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180924183637.16423-1-yskoh@mellanox.com>

Monday, September 24, 2018 9:37 PM, Yongseok Koh:
> Subject: [PATCH 1/2] net/mlx4: support externally allocated static memory
> 
> When MLX PMD registers memory for DMA, it accesses the global memseg
> list of DPDK to maximize the range of registration so that LKey search can be
> more efficient. Granularity of MR registration is per page.
> 
> Externally allocated memory shouldn't be used for DMA because it can't be
> searched in the memseg list and free event can't be tracked by DPDK. If it is
> used, the following error will occur:
> 
> 	net_mlx5: port 0 unable to find virtually contiguous chunk for
> 	address (0x5600017587c0). rte_memseg_contig_walk() failed.
> 
> There's a pending patchset [1] which enables externally allocated memory.
> Once it is merged, users can register their own memory out of EAL then that
> will resolve this issue.
> 
> Meanwhile, if the external memory is static (allocated on startup and never
> freed), such memory can also be registered by little tweak in the code.
> 
> [1] http://patches.dpdk.org/project/dpdk/list/?series=1415
> 
> This patch is not a bug fix but needs to be included in stable versions.
> 
> Fixes: 9797bfcce1c9 ("net/mlx4: add new memory region support")
> Cc: stable@dpdk.org
> Cc: "Damjan Marion (damarion)" <damarion@cisco.com>
> Cc: Ed Warnicke <hagbard@gmail.com>
> 
> Signed-off-by: Yongseok Koh <yskoh@mellanox.com>
> ---

Series applied to next-net-mlx, thanks. 

      parent reply	other threads:[~2018-10-07 11:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24 18:36 Yongseok Koh
2018-09-24 18:36 ` [dpdk-stable] [PATCH 2/2] net/mlx5: " Yongseok Koh
2018-10-07 11:00 ` 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=DB7PR05MB4426105A3BB0CA0A0744AC0DC3E50@DB7PR05MB4426.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=damarion@cisco.com \
    --cc=dev@dpdk.org \
    --cc=hagbard@gmail.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).