From: Eliezer Tamir <eliezer.tamir@linux.intel.com>
To: David Miller <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Don Skidmore <donald.c.skidmore@intel.com>,
e1000-devel@lists.sourceforge.net,
Willem de Bruijn <willemb@google.com>,
Eric Dumazet <erdnetdev@gmail.com>,
Ben Hutchings <bhutchings@solarflare.com>,
Andi Kleen <andi@firstfloor.org>, HPA <hpa@zytor.com>,
Eilon Greenstien <eilong@broadcom.com>,
Or Gerlitz <or.gerlitz@gmail.com>,
Amir Vadai <amirv@mellanox.com>,
Alex Rosenbaum <alexr@mellanox.com>,
Avner Ben Hanoch <avnerb@mellanox.com>,
Or Kehati <ork@mellanox.com>,
sockperf-dev@googlegroups.com,
Eliezer Tamir <eliezer@tamir.org.il>
Subject: [PATCH v5 net-next 0/4] net: low latency sockets follow ups
Date: Fri, 14 Jun 2013 16:33:14 +0300 [thread overview]
Message-ID: <20130614133314.6126.77315.stgit@ladj378.jer.intel.com> (raw)
David,
Here are three clean up patches, plus one that adds a socket option for LLS.
Patch 1 converts sysctl_net_ll_poll into an unsigned int
Patch 2 converts low latency sockets to sched_clock.
Patch 3 removes the config menu for NET_LL_RX_POLL and defaults to y.
Patch 4 adds an SO_LL socket option to allow per-socket control of busy polling.
I will reply to this thread with a patch to sockperf that enables
the socket option. (unchanged from v2)
Again, thanks to everyone for their comments.
-Eliezer
Change log:
v5
- use time_after64() instead of time_after, suggested by Eric Dumazet.
v4
- Fixed possible overflow, pointed out by Eric Dumazet.
(reordered the patches)
v3
- Suggested by David Miller and Stephen Hemminger:
added a patch to covert from get_cycles() to sched_clock(),
remove dependency on X86_TSC.
- Suggested by Eric Dumazet:
un-exported sysctl_net_ll_poll since for now it's not needed in modules.
v2
- added a patch to convert sysctl_net_ll_poll into an unsigned int.
- suggested by Eric Dimazet: treat sk_ll_usec as a u_int rather than a u_long.
- suggested by Ben Huchings: allow unprivileged user to decrease SO_LL value,
correct return value when operation is not allowed.
next reply other threads:[~2013-06-14 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 13:33 Eliezer Tamir [this message]
2013-06-14 13:33 ` [PATCH v5 net-next 1/4] net: change sysctl_net_ll_poll into an unsigned int Eliezer Tamir
2013-06-14 13:33 ` [PATCH v5 net-next 2/4] net: convert low latency sockets to sched_clock() Eliezer Tamir
2013-06-14 13:33 ` [PATCH v5 net-next 3/4] net: remove NET_LL_RX_POLL config menue Eliezer Tamir
2013-06-14 13:33 ` [PATCH v5 net-next 4/4] net: add socket option for low latency polling Eliezer Tamir
2013-06-14 13:36 ` [PATCH v2 sockperf] sockperf: add SO_LL socketop support Eliezer Tamir
2013-06-17 22:48 ` [PATCH v5 net-next 0/4] net: low latency sockets follow ups 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=20130614133314.6126.77315.stgit@ladj378.jer.intel.com \
--to=eliezer.tamir@linux.intel.com \
--cc=alexr@mellanox.com \
--cc=amirv@mellanox.com \
--cc=andi@firstfloor.org \
--cc=avnerb@mellanox.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=eilong@broadcom.com \
--cc=eliezer@tamir.org.il \
--cc=erdnetdev@gmail.com \
--cc=hpa@zytor.com \
--cc=jesse.brandeburg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=ork@mellanox.com \
--cc=sockperf-dev@googlegroups.com \
--cc=willemb@google.com \
/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).