From: Jason Gunthorpe <jgg@ziepe.ca>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@mellanox.com>,
RDMA mailing list <linux-rdma@vger.kernel.org>,
Haggai Eran <haggaie@mellanox.com>,
Saeed Mahameed <saeedm@mellanox.com>,
linux-netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH rdma-next v1 0/5] Cleanup of CONFIG_INFINIBAND_ON_DEMAND_PAGING usage
Date: Mon, 7 Jan 2019 11:31:28 -0700 [thread overview]
Message-ID: <20190107183128.GA4613@ziepe.ca> (raw)
In-Reply-To: <20181223091418.26218-1-leon@kernel.org>
On Sun, Dec 23, 2018 at 11:14:13AM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@mellanox.com>
>
> Changelog v0->v1:
> * Don't set ODP caps always (patch #2)
> * Set invalidate_range callback based on device_cap only
>
> -------------------------------------------------------------------------------
>
> Hi,
>
> As a followup to Jason's request to rethink CONFIG_INFINIBAND_ON_DEMAND_PAGING
> usage, this series cleans mlx5_ib and RDMA/core code and it is based on accepted
> patch https://patchwork.kernel.org/patch/10735547/
>
> I think that we will see more patches in that area, I would like to
> remove CONFIG_INFINIBAND_ON_DEMAND_PAGING completely.
>
> Thanks
>
> Leon Romanovsky (5):
> RDMA: Clean structures from CONFIG_INFINIBAND_ON_DEMAND_PAGING
> RDMA/core: Don't depend device ODP capabilities on kconfig option
> RDMA/mlx5: Introduce and reuse helper to identify ODP MR
> RDMA/mlx5: Embed into the code flow the ODP config option
> RDMA/mlx5: Delete declaration of already removed function
This doesn't apply anymore, can you resend it please?
Jason
next prev parent reply other threads:[~2019-01-07 18:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 9:14 [PATCH rdma-next v1 0/5] Cleanup of CONFIG_INFINIBAND_ON_DEMAND_PAGING usage Leon Romanovsky
2018-12-23 9:14 ` [PATCH rdma-next v1 1/5] RDMA: Clean structures from CONFIG_INFINIBAND_ON_DEMAND_PAGING Leon Romanovsky
2018-12-23 9:14 ` [PATCH rdma-next v1 2/5] RDMA/core: Don't depend device ODP capabilities on kconfig option Leon Romanovsky
2018-12-23 9:14 ` [PATCH rdma-next v1 3/5] RDMA/mlx5: Introduce and reuse helper to identify ODP MR Leon Romanovsky
2018-12-23 9:14 ` [PATCH rdma-next v1 4/5] RDMA/mlx5: Embed into the code flow the ODP config option Leon Romanovsky
2018-12-23 9:14 ` [PATCH mlx5-next v1 5/5] RDMA/mlx5: Delete declaration of already removed function Leon Romanovsky
2019-01-07 18:31 ` Jason Gunthorpe [this message]
2019-01-08 6:18 ` [PATCH rdma-next v1 0/5] Cleanup of CONFIG_INFINIBAND_ON_DEMAND_PAGING usage Leon Romanovsky
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=20190107183128.GA4613@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dledford@redhat.com \
--cc=haggaie@mellanox.com \
--cc=leon@kernel.org \
--cc=leonro@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@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).