From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: santosh.shilimkar@oracle.com
Subject: [net-next][PATCH v2 2/2] rds: add sysctl for rds support of On-Demand-Paging
Date: Mon, 29 Apr 2019 16:37:20 -0700 [thread overview]
Message-ID: <1556581040-4812-3-git-send-email-santosh.shilimkar@oracle.com> (raw)
In-Reply-To: <1556581040-4812-1-git-send-email-santosh.shilimkar@oracle.com>
RDS doesn't support RDMA on memory apertures that require On Demand
Paging (ODP), such as FS DAX memory. A sysctl is added to indicate
whether RDMA requiring ODP is supported.
Reviewed-by: Håkon Bugge <haakon.bugge@oracle.com>
Reviewed-tested-by: Zhu Yanjun <yanjun.zhu@oracle.com>
Signed-off-by: Hans Westgaard Ry <hans.westgaard.ry@oracle.com>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@oracle.com>
---
net/rds/ib.h | 1 +
net/rds/ib_sysctl.c | 8 ++++++++
2 files changed, 9 insertions(+)
diff --git a/net/rds/ib.h b/net/rds/ib.h
index 67a715b..80e11ef 100644
--- a/net/rds/ib.h
+++ b/net/rds/ib.h
@@ -457,5 +457,6 @@ unsigned int rds_ib_stats_info_copy(struct rds_info_iterator *iter,
extern unsigned long rds_ib_sysctl_max_unsig_bytes;
extern unsigned long rds_ib_sysctl_max_recv_allocation;
extern unsigned int rds_ib_sysctl_flow_control;
+extern unsigned int rds_ib_sysctl_odp_support;
#endif
diff --git a/net/rds/ib_sysctl.c b/net/rds/ib_sysctl.c
index e4e41b3..7cc02cd 100644
--- a/net/rds/ib_sysctl.c
+++ b/net/rds/ib_sysctl.c
@@ -60,6 +60,7 @@
* will cause credits to be added before protocol negotiation.
*/
unsigned int rds_ib_sysctl_flow_control = 0;
+unsigned int rds_ib_sysctl_odp_support;
static struct ctl_table rds_ib_sysctl_table[] = {
{
@@ -103,6 +104,13 @@
.mode = 0644,
.proc_handler = proc_dointvec,
},
+ {
+ .procname = "odp_support",
+ .data = &rds_ib_sysctl_odp_support,
+ .maxlen = sizeof(rds_ib_sysctl_odp_support),
+ .mode = 0444,
+ .proc_handler = proc_dointvec,
+ },
{ }
};
--
1.9.1
next prev parent reply other threads:[~2019-04-29 23:37 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 23:37 [net-next][PATCH v2 0/2] rds: handle unsupported rdma request to fs dax memory Santosh Shilimkar
2019-04-29 23:37 ` [net-next][PATCH v2 1/2] " Santosh Shilimkar
2019-05-01 7:44 ` Leon Romanovsky
2019-05-01 17:54 ` Santosh Shilimkar
2019-05-02 6:21 ` Leon Romanovsky
2019-05-02 17:52 ` Santosh Shilimkar
2019-05-05 6:28 ` Leon Romanovsky
2019-05-06 16:39 ` Santosh Shilimkar
2019-05-10 12:54 ` Jason Gunthorpe
2019-05-10 16:11 ` Santosh Shilimkar
2019-05-10 17:55 ` Jason Gunthorpe
2019-05-10 18:02 ` santosh.shilimkar
2019-05-10 18:07 ` Jason Gunthorpe
2019-05-10 18:58 ` santosh.shilimkar
2019-05-10 19:20 ` Jason Gunthorpe
2019-05-10 19:38 ` Santosh Shilimkar
2019-05-10 19:47 ` Jason Gunthorpe
2019-05-10 20:12 ` Santosh Shilimkar
2019-05-10 20:39 ` Jason Gunthorpe
2019-04-29 23:37 ` Santosh Shilimkar [this message]
2019-05-01 7:45 ` [net-next][PATCH v2 2/2] rds: add sysctl for rds support of On-Demand-Paging Leon Romanovsky
2019-05-01 17:54 ` Santosh Shilimkar
2019-05-02 6:18 ` Leon Romanovsky
2019-05-02 17:59 ` Santosh Shilimkar
2019-05-05 6:22 ` Leon Romanovsky
2019-05-06 16:37 ` Santosh Shilimkar
2019-05-10 13:02 ` Jason Gunthorpe
2019-05-10 16:13 ` Santosh Shilimkar
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=1556581040-4812-3-git-send-email-santosh.shilimkar@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
/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).