linux-kernel - Re: [PATCH v3 net-next 0/4] net: low latency sockets follow ups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130613.174339.1937633112098047039.davem@davemloft.net>
Date:	Thu, 13 Jun 2013 17:43:39 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	eliezer.tamir@...ux.intel.com
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	jesse.brandeburg@...el.com, donald.c.skidmore@...el.com,
	e1000-devel@...ts.sourceforge.net, willemb@...gle.com,
	erdnetdev@...il.com, bhutchings@...arflare.com,
	andi@...stfloor.org, hpa@...or.com, eilong@...adcom.com,
	or.gerlitz@...il.com, amirv@...lanox.com, alexr@...lanox.com,
	avnerb@...lanox.com, ork@...lanox.com,
	sockperf-dev@...glegroups.com, eliezer@...ir.org.il
Subject: Re: [PATCH v3 net-next 0/4] net: low latency sockets follow ups

From: Eliezer Tamir <eliezer.tamir@...ux.intel.com>
Date: Thu, 13 Jun 2013 17:46:13 +0300

> Here are three clean up patches, plus one that adds a socket option for LLS.
> 
> Patch 1 converts low latency sockets to sched_clock.
> Patch 2 removes the config menu for NET_LL_RX_POLL and defaults to y.
> Patch 3 converts sysctl_net_ll_poll into an unsigned int
> 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.

Please respin with the overflow introduced by patch #3 corrected, everything
else looks fine to me.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/