public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Ursula Braun <ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: hch-jcswGhMUV9g@public.gmane.org,
	schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org,
	heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org,
	hwippel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	raspl-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: [RFC net-next 06/10] net/smc: remove Kconfig warning
Date: Thu, 20 Jul 2017 14:09:42 +0200	[thread overview]
Message-ID: <20170720120946.67234-7-ubraun@linux.vnet.ibm.com> (raw)
In-Reply-To: <20170720120946.67234-1-ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>

Now separate memory regions are created and registered for separate
RMBs. The unsafe_global_rkey of the protection domain is no longer
used. Thus the exposing memory warning can be removed.

Signed-off-by: Ursula Braun <ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
---
 net/smc/Kconfig | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/net/smc/Kconfig b/net/smc/Kconfig
index 33954852f3f8..c717ef0896aa 100644
--- a/net/smc/Kconfig
+++ b/net/smc/Kconfig
@@ -8,10 +8,6 @@ config SMC
 	  The Linux implementation of the SMC-R solution is designed as
 	  a separate socket family SMC.
 
-	  Warning: SMC will expose all memory for remote reads and writes
-	  once a connection is established.  Don't enable this option except
-	  for tightly controlled lab environment.
-
 	  Select this option if you want to run SMC socket applications
 
 config SMC_DIAG
-- 
2.11.2

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-07-20 12:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-20 12:09 [RFC net-next 00/10] net/smc: get rid of unsafe_global_rkey Ursula Braun
     [not found] ` <20170720120946.67234-1-ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-07-20 12:09   ` [RFC net-next 01/10] net/smc: serialize connection creation in all cases Ursula Braun
2017-07-20 12:09   ` [RFC net-next 02/10] net/smc: shorten local bufsize variables Ursula Braun
2017-07-20 12:09   ` [RFC net-next 03/10] net/smc: introduce sg-logic for RMBs Ursula Braun
     [not found]     ` <20170720120946.67234-4-ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-07-20 15:13       ` Sagi Grimberg
2017-07-20 12:09   ` [RFC net-next 04/10] net/smc: use separate memory regions " Ursula Braun
2017-07-20 12:09   ` [RFC net-next 05/10] net/smc: register RMB-related memory region Ursula Braun
     [not found]     ` <20170720120946.67234-6-ubraun-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2017-07-20 15:17       ` Sagi Grimberg
     [not found]         ` <8df0459f-b2be-53f1-a7c3-388ca22a128c-NQWnxTmZq1alnMjI0IkVqw@public.gmane.org>
2017-07-20 15:47           ` Parav Pandit
2017-07-21  7:47           ` Ursula Braun
2017-07-20 12:09   ` Ursula Braun [this message]
2017-07-20 12:09   ` [RFC net-next 07/10] net/smc: introduce sg-logic for send buffers Ursula Braun
2017-07-20 12:09   ` [RFC net-next 08/10] net/smc: common functions for RMBs and " Ursula Braun
2017-07-20 12:09   ` [RFC net-next 09/10] net/smc: cleanup function __smc_buf_create() Ursula Braun
2017-07-20 12:09   ` [RFC net-next 10/10] net/smc: synchronize buffer usage with device Ursula Braun
2017-07-20 15:06   ` [RFC net-next 00/10] net/smc: get rid of unsafe_global_rkey Sagi Grimberg

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=20170720120946.67234-7-ubraun@linux.vnet.ibm.com \
    --to=ubraun-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=hch-jcswGhMUV9g@public.gmane.org \
    --cc=heiko.carstens-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
    --cc=hwippel-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=raspl-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=schwidefsky-tA70FqPdS9bQT0dZR+AlfA@public.gmane.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