From: Or Gerlitz <ogerlitz@mellanox.com>
To: Roland Dreier <roland@kernel.org>
Cc: Or Gerlitz <gerlitz.or@gmail.com>,
Latchesar Ionkov <lionkov@lanl.gov>,
"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>,
Haggai Eran <haggaie@mellanox.com>
Subject: Re: [PATCH v1 for-next 00/16] On demand paging
Date: Wed, 17 Sep 2014 18:18:46 +0300 [thread overview]
Message-ID: <5419A656.2050004@mellanox.com> (raw)
In-Reply-To: <CAJ3xEMhSZcrN0_nurc=-sUT+KM3vFgAD6XJjjA-eK0-Jyeut0Q@mail.gmail.com>
On 9/13/2014 12:16 AM, Or Gerlitz wrote:
> Per your request we provided the information on tests conducted with
> the patches.
>
> Note that the patches can't really disrupt existing applications that
> don't set the new IB_ACCESS_ON_DEMAND MR flag when they register
> memory. Also the whole set of changes to the umem area is dependent on building with
> CONFIG_INFINIBAND_ON_DEMAND_PAGING -- all in all, everything is in
> place for protecting against potential regression that this series
> could introduce.
>
> As you didn't provide any feedback for > six months, and we have all
> the above in place (report on stability tests, performance data and
> mechanics to avoid regressions) I think it would be fair to get this
> picked for the coming merge window, thoughts?
Roland,
Can you please comment here, not only that you didn't provide any
feedback on the patches, you
are even not willing to respond if the the data we gave addresses your
questions on testing and performance. Are you planning to pick this to
the next merge window?
Or.
prev parent reply other threads:[~2014-09-17 15:18 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
2014-09-10 9:28 ` Sagi Grimberg
2014-09-12 21:16 ` Or Gerlitz
2014-09-17 15:18 ` Or Gerlitz [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=5419A656.2050004@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=gerlitz.or@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=haggaie@mellanox.com \
--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