From: Eliezer Tamir <eliezer.tamir@linux.intel.com>
To: Micahel Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man@vger.kernel.org, David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Eliezer Tamir <eliezer@tamir.org.il>
Subject: [PATCH] socket.7: add description for SO_BUSY_POLL
Date: Wed, 10 Jul 2013 15:17:45 +0300 [thread overview]
Message-ID: <20130710121745.13118.86907.stgit@ladj378.jer.intel.com> (raw)
Add description for the SO_BUSY_POLL socket option to the socket(7) manpage.
Signed-off-by: Eliezer Tamir <eliezer.tamir@linux.intel.com>
---
man7/socket.7 | 25 +++++++++++++++++++++++++
1 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/man7/socket.7 b/man7/socket.7
index f2213eb..27603c9 100644
--- a/man7/socket.7
+++ b/man7/socket.7
@@ -694,6 +694,31 @@ for details on control messages.
Gets the socket type as an integer (e.g.,
.BR SOCK_STREAM ).
This socket option is read-only.
+.TP
+.B SO_BUSY_POLL
+Sets the approximate time in microseconds to busy poll on a blocking receive
+when there is no data. Increasing this value requires
+.BR CAP_NET_ADMIN .
+The default for this option is controlled by the
+.I /proc/sys/net/core/busy_read
+file.
+
+The value in the
+.I /proc/sys/net/core/busy_poll
+file determines how long
+.BR select (2)
+and
+.BR poll (2)
+will busy poll when they operate on sockets with
+.BR SO_BUSY_POLL
+set and no events to report are found.
+
+In both cases busy polling will only be done when the socket last received data
+from a network device that supports this option.
+
+While busy polling my improve latency of some application, care must be
+taken when using it since this will increase both CPU utilization power usage.
+
.SS Signals
When writing onto a connection-oriented socket that has been shut down
(by the local or the remote end)
next reply other threads:[~2013-07-10 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-10 12:17 Eliezer Tamir [this message]
2013-07-10 12:55 ` [PATCH] socket.7: add description for SO_BUSY_POLL Rasmus Villemoes
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=20130710121745.13118.86907.stgit@ladj378.jer.intel.com \
--to=eliezer.tamir@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=eliezer@tamir.org.il \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--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