netdev - Re: [net-next PATCH] [RFC] [v2] net: add option to enable error queue packets waking select

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: <20130331.194522.608435617919159346.davem@davemloft.net>
Date:	Sun, 31 Mar 2013 19:45:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	jacob.e.keller@...el.com
Cc:	netdev@...r.kernel.org, jeffrey.t.kirsher@...el.com,
	richardcochran@...il.com, matthew.vick@...el.com
Subject: Re: [net-next PATCH] [RFC] [v2] net: add option to enable error
 queue packets waking select

From: Jacob Keller <jacob.e.keller@...el.com>
Date: Thu, 28 Mar 2013 14:19:25 -0700

> Currently, when a socket receives something on the error queue it only wakes up
> the socket on select if it is in the "read" list, that is the socket has
> something to read. It is useful also to wake the socket if it is in the error
> list, which would enable software to wait on error queue packets without waking
> up for regular data on the socket. The main use case is for receiving
> timestamped transmit packets which return the timestamp to the socket via the
> error queue. This enables an application to select on the socket for the error
> queue only instead of for the regular traffic.
> 
> -v2-
> * Added the SO_SELECT_ERR_QUEUE socket option to every architechture specific file
> * Modified every socket poll function that checks error queue
> 
> Signed-off-by: Jacob Keller <jacob.e.keller@...el.com>

Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html