All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Yongseok Koh <yskoh@mellanox.com>
Cc: shahafs@mellanox.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 5/6] net/mlx4: add control of excessive memory pinning by kernel
Date: Mon, 13 May 2019 21:54:37 -0700	[thread overview]
Message-ID: <20190513215437.65b8f225@hermes.lan> (raw)
In-Reply-To: <20190513215222.46f6e3fb@hermes.lan>

On Mon, 13 May 2019 21:52:22 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:

> On Mon,  1 Apr 2019 14:17:56 -0700
> Yongseok Koh <yskoh@mellanox.com> wrote:
> 
> > +- ``mr_ext_memseg_en`` parameter [int]
> > +
> > +  A nonzero value enables extending memseg when registering DMA memory. If
> > +  enabled, the number of entries in MR (Memory Region) lookup table on datapath
> > +  is minimized and it benefits performance. On the other hand, it worsens memory
> > +  utilization because registered memory is pinned by kernel driver. Even if a
> > +  page in the extended chunk is freed, that doesn't become reusable until the
> > +  entire memory is freed.
> > +
> > +  Enabled by default.
> > +  
> 
> This module parameter does not appear in the upstream Linux kernel drivers (even 5.2).
> What code are you referring to?

Nevermind, it is a DPDK not kernel parameter.

  reply	other threads:[~2019-05-14  4:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  7:41 [PATCH 0/6] net/mlx: enable secondary process to register DMA memory Yongseok Koh
2019-03-07  7:41 ` [PATCH 1/6] net/mlx: remove debug messages on datapath Yongseok Koh
2019-03-07  7:41 ` [PATCH 2/6] net/mlx5: fix external memory registration Yongseok Koh
2019-03-07  7:41 ` [PATCH 3/6] net/mlx5: add control of excessive memory pinning by kernel Yongseok Koh
2019-03-07  7:41 ` [PATCH 4/6] net/mlx5: enable secondary process to register DMA memory Yongseok Koh
2019-03-07  7:41 ` [PATCH 5/6] net/mlx4: add control of excessive memory pinning by kernel Yongseok Koh
2019-03-07  7:41 ` [PATCH 6/6] net/mlx4: enable secondary process to register DMA memory Yongseok Koh
2019-03-07  7:55 ` [PATCH 0/6] net/mlx: " Yongseok Koh
2019-03-14 12:45 ` Shahaf Shuler
2019-03-25 19:22 ` [PATCH v2 " Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 1/6] net/mlx: remove debug messages on datapath Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 2/6] net/mlx5: fix external memory registration Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 3/6] net/mlx5: add control of excessive memory pinning by kernel Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 4/6] net/mlx5: enable secondary process to register DMA memory Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 5/6] net/mlx4: add control of excessive memory pinning by kernel Yongseok Koh
2019-03-25 19:22   ` [PATCH v2 6/6] net/mlx4: enable secondary process to register DMA memory Yongseok Koh
2019-04-01 21:17 ` [PATCH v3 0/6] net/mlx: " Yongseok Koh
2019-04-01 21:17   ` [PATCH v3 1/6] net/mlx: remove debug messages on datapath Yongseok Koh
2019-04-01 21:17   ` [PATCH v3 2/6] net/mlx5: fix external memory registration Yongseok Koh
2019-04-01 21:17   ` [PATCH v3 3/6] net/mlx5: add control of excessive memory pinning by kernel Yongseok Koh
2019-04-01 21:17   ` [PATCH v3 4/6] net/mlx5: enable secondary process to register DMA memory Yongseok Koh
2019-04-01 21:17   ` [PATCH v3 5/6] net/mlx4: add control of excessive memory pinning by kernel Yongseok Koh
2019-05-14  4:52     ` [dpdk-dev] " Stephen Hemminger
2019-05-14  4:54       ` Stephen Hemminger [this message]
2019-04-01 21:17   ` [PATCH v3 6/6] net/mlx4: enable secondary process to register DMA memory Yongseok Koh
2019-04-02  7:13   ` [PATCH v3 0/6] net/mlx: " Shahaf Shuler

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=20190513215437.65b8f225@hermes.lan \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=shahafs@mellanox.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.