From: Daniel Borkmann <dborkman@redhat.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org
Subject: [PATCH] netlink: kconfig: move mmap i/o into netlink kconfig
Date: Wed, 1 May 2013 13:37:20 +0200 [thread overview]
Message-ID: <1367408240-30320-1-git-send-email-dborkman@redhat.com> (raw)
Currently, in menuconfig, Netlink's new mmaped IO is the very first
entry under the ``Networking support'' item and comes even before
``Networking options'':
[ ] Netlink: mmaped IO
Networking options --->
...
Lets move this into ``Networking options'' under netlink's Kconfig,
since this might be more appropriate. Introduced by commit ccdfcc398
(``netlink: mmaped netlink: ring setup'').
Signed-off-by: Daniel Borkmann <dborkman@redhat.com>
---
net/Kconfig | 9 ---------
net/netlink/Kconfig | 9 +++++++++
2 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/net/Kconfig b/net/Kconfig
index 1a22216..2ddc904 100644
--- a/net/Kconfig
+++ b/net/Kconfig
@@ -23,15 +23,6 @@ menuconfig NET
if NET
-config NETLINK_MMAP
- bool "Netlink: mmaped IO"
- help
- This option enables support for memory mapped netlink IO. This
- reduces overhead by avoiding copying data between kernel- and
- userspace.
-
- If unsure, say N.
-
config WANT_COMPAT_NETLINK_MESSAGES
bool
help
diff --git a/net/netlink/Kconfig b/net/netlink/Kconfig
index 5d6e8c0..2c5e95e 100644
--- a/net/netlink/Kconfig
+++ b/net/netlink/Kconfig
@@ -2,6 +2,15 @@
# Netlink Sockets
#
+config NETLINK_MMAP
+ bool "NETLINK: mmaped IO"
+ ---help---
+ This option enables support for memory mapped netlink IO. This
+ reduces overhead by avoiding copying data between kernel- and
+ userspace.
+
+ If unsure, say N.
+
config NETLINK_DIAG
tristate "NETLINK: socket monitoring interface"
default n
--
1.7.11.7
next reply other threads:[~2013-05-01 11:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 11:37 Daniel Borkmann [this message]
2013-05-01 19:03 ` [PATCH] netlink: kconfig: move mmap i/o into netlink kconfig David Miller
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=1367408240-30320-1-git-send-email-dborkman@redhat.com \
--to=dborkman@redhat.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).