From: Sowmini Varadhan <sowmini.varadhan@oracle.com>
To: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: chien.yen@oracle.com, davem@davemloft.net,
rds-devel@oss.oracle.com, agrover@redhat.com, clm@fb.com,
zab@zabbo.net, ajaykumar.hotchandani@oracle.com,
sergei.shtylyov@cogentembedded.com,
Sowmini Varadhan <sowmini.varadhan@oracle.com>
Subject: [PATCHv2 1/6] RDS: Re-add pf/sol access via sysctl
Date: Thu, 2 Apr 2015 10:19:35 -0400 [thread overview]
Message-ID: <6df5ee9a571eb865e5a26f367e18c34182de9e17.1427983908.git.sowmini.varadhan@oracle.com> (raw)
In-Reply-To: <cover.1427983908.git.sowmini.varadhan@oracle.com>
In-Reply-To: <cover.1427983908.git.sowmini.varadhan@oracle.com>
Although RDS has an official PF_RDS value now, existing software
expects to look for rds sysctls to determine it. We need to maintain
these for now, for backwards compatibility.
Original patch by Andy Grover
Signed-off-by: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Reviewed-by: Ajaykumar Hotchandani <ajaykumar.hotchandani@oracle.com>
---
net/rds/sysctl.c | 20 ++++++++++++++++++++
1 files changed, 20 insertions(+), 0 deletions(-)
diff --git a/net/rds/sysctl.c b/net/rds/sysctl.c
index c173f69..5fbe9e6 100644
--- a/net/rds/sysctl.c
+++ b/net/rds/sysctl.c
@@ -49,6 +49,12 @@ unsigned int rds_sysctl_max_unacked_bytes = (16 << 20);
unsigned int rds_sysctl_ping_enable = 1;
+/* We have official values, but must maintain the sysctl interface for existing
+ * software that expects to find these values here.
+ */
+static int rds_sysctl_pf_rds = PF_RDS;
+static int rds_sysctl_sol_rds = SOL_RDS;
+
static struct ctl_table rds_sysctl_rds_table[] = {
{
.procname = "reconnect_min_delay_ms",
@@ -69,6 +75,20 @@ static struct ctl_table rds_sysctl_rds_table[] = {
.extra2 = &rds_sysctl_reconnect_max,
},
{
+ .procname = "pf_rds",
+ .data = &rds_sysctl_pf_rds,
+ .maxlen = sizeof(int),
+ .mode = 0444,
+ .proc_handler = proc_dointvec,
+ },
+ {
+ .procname = "sol_rds",
+ .data = &rds_sysctl_sol_rds,
+ .maxlen = sizeof(int),
+ .mode = 0444,
+ .proc_handler = proc_dointvec,
+ },
+ {
.procname = "max_unacked_packets",
.data = &rds_sysctl_max_unacked_packets,
.maxlen = sizeof(int),
--
1.7.1
next prev parent reply other threads:[~2015-04-02 14:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 14:19 [PATCHv2 0/6] RDS: RDS core bug fixes Sowmini Varadhan
2015-04-02 14:19 ` Sowmini Varadhan [this message]
2015-04-02 14:19 ` [PATCHv2 2/6] RDS: only use passive connections when addresses match Sowmini Varadhan
2015-04-02 14:19 ` [PATCHv2 3/6] rds: check for excessive looping in rds_send_xmit Sowmini Varadhan
2015-04-02 18:08 ` David Miller
2015-04-02 14:19 ` [PATCHv2 4/6] RDS: make sure not to loop forever inside rds_send_xmit Sowmini Varadhan
2015-04-02 14:19 ` [PATCHv2 5/6] RDS: rds_send_xmit is called under a spinlock, lets not do a cond_resched() Sowmini Varadhan
2015-04-02 14:19 ` [PATCHv2 6/6] RDS: don't trust the LL_SEND_FULL bit Sowmini Varadhan
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=6df5ee9a571eb865e5a26f367e18c34182de9e17.1427983908.git.sowmini.varadhan@oracle.com \
--to=sowmini.varadhan@oracle.com \
--cc=agrover@redhat.com \
--cc=ajaykumar.hotchandani@oracle.com \
--cc=chien.yen@oracle.com \
--cc=clm@fb.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rds-devel@oss.oracle.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=zab@zabbo.net \
/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).