From: Haggai Eran <haggaie@mellanox.com>
To: Roland Dreier <roland@kernel.org>, Latchesar Ionkov <lionkov@lanl.gov>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sagi Grimberg <sagig@mellanox.com>,
"Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1 for-next 00/16] On demand paging
Date: Wed, 10 Sep 2014 11:51:47 +0300 [thread overview]
Message-ID: <54101123.2080208@mellanox.com> (raw)
In-Reply-To: <540F0CD8.9070002@mellanox.com>
On 09/09/2014 17:21, Haggai Eran wrote:
> On 04/09/2014 00:15, Roland Dreier wrote:
>> Have you done any review or testing of these changes? If so can you
>> share the results?
>
> We have tested this feature thoroughly inside Mellanox. We ran random
> tests that performed MR registrations, memory mappings and unmappings,
> calls to madvise with MADV_DONTNEED for invalidations, sending and
> receiving of data, and RDMA operations. The test validated the integrity
> of the data, and we verified the integrity of kernel memory by running
> the tests under a debugging kernel.
We wanted to add regarding performance testing of these patches, we have
tested ODP on several setups, including low-level RDMA micro-benchmarks,
MPI applications, and iSER. In all cases, ODP delivers the *same*
bare-metal performance as obtained with standard MRs, in terms of both
BW and latency. In addition, performance of standard MRs is not affected
by the presence of ODP applications.
The main benefits of ODP is the simplified programming model, simplified
management, and avoiding worst-case memory commitment.
For example, we were able to run multiple concurrent instances of iSER
targets, allowing over-commitment that otherwise wouldn’t be possible.
In the MPI case, both IMB (Pallas) and applications achieved the same
performance as the pin-down cache, with minimal memory locking
privileges while avoiding any glibc hooks for detecting invalidations.
Regards,
Haggai
next prev parent reply other threads:[~2014-09-10 8:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1404377069-20585-1-git-send-email-haggaie@mellanox.com>
[not found] ` <5405D2D8.1040700@mellanox.com>
2014-09-03 20:21 ` [PATCH v1 for-next 00/16] On demand paging Or Gerlitz
[not found] ` <CAOha14xthZHSpS_T+XRgZcPqwaZvtMw0iGTzKjTyjdBuLhJ4Eg@mail.gmail.com>
2014-09-03 21:15 ` Roland Dreier
2014-09-04 17:45 ` Jerome Glisse
2014-09-09 14:21 ` Haggai Eran
2014-09-10 8:51 ` Haggai Eran [this message]
2014-09-10 9:28 ` Sagi Grimberg
2014-09-12 21:16 ` Or Gerlitz
2014-09-17 15:18 ` Or Gerlitz
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=54101123.2080208@mellanox.com \
--to=haggaie@mellanox.com \
--cc=gerlitz.or@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lionkov@lanl.gov \
--cc=roland@kernel.org \
--cc=sagig@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