From: Shahaf Shuler <shahafs@mellanox.com>
To: "Nélio Laranjeiro" <nelio.laranjeiro@6wind.com>,
"Xueming(Steven) Li" <xuemingl@mellanox.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] net/mlx5: mmap uar address around huge pages
Date: Thu, 25 Jan 2018 16:33:52 +0000 [thread overview]
Message-ID: <VI1PR05MB3149229A59E538BF1F11D4A1C3E10@VI1PR05MB3149.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <20180125160105.vm75fsol3y3z3cix@laranjeiro-vm.dev.6wind.com>
Thursday, January 25, 2018 6:01 PM, Nélio Laranjeiro:
> Subject: Re: [PATCH v2] net/mlx5: mmap uar address around huge pages
>
> On Thu, Jan 25, 2018 at 11:00:24PM +0800, Xueming Li wrote:
> > Reserving the memory space for the UAR near huge pages helps to
> > **reduce** the cases where the secondary process cannot start. Those
> > pages being physical pages they must be mapped at the same virtual
> > address as in the primary process to have a working secondary process.
> >
> > As this remap is almost the latest being done by the processes
> > (libraries, heaps, stacks are already loaded), similar to huge pages,
> > there is **no guarantee** this mechanism will always work.
> >
> > Signed-off-by: Xueming Li <xuemingl@mellanox.com>
>
> As it does not break anything...
>
> Acked-by: Nelio Laranjeiro <nelio.laranjeiro@6wind.com>
Applied to next-net-mlx, thanks.
>
> --
> Nélio Laranjeiro
> 6WIND
prev parent reply other threads:[~2018-01-25 16:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 15:08 [dpdk-dev] [PATCH] net/mlx5: remmap UAR address for multiple process Xueming Li
2018-01-22 14:53 ` Nélio Laranjeiro
2018-01-23 9:50 ` Xueming(Steven) Li
2018-01-23 13:31 ` Nélio Laranjeiro
2018-01-23 14:16 ` Xueming(Steven) Li
2018-01-25 15:00 ` [dpdk-dev] [PATCH v2] net/mlx5: mmap uar address around huge pages Xueming Li
2018-01-25 16:01 ` Nélio Laranjeiro
2018-01-25 16:33 ` 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=VI1PR05MB3149229A59E538BF1F11D4A1C3E10@VI1PR05MB3149.eurprd05.prod.outlook.com \
--to=shahafs@mellanox.com \
--cc=dev@dpdk.org \
--cc=nelio.laranjeiro@6wind.com \
--cc=xuemingl@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).