netdev - Re: [PATCH net-next v3 0/2] ipv4: per-datagram IP_TOS and IP

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: <20130928.152217.259922330845282884.davem@davemloft.net>
Date:	Sat, 28 Sep 2013 15:22:17 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ffusco@...hat.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH net-next v3 0/2] ipv4: per-datagram IP_TOS and IP_TTL
 via sendmsg()

From: Francesco Fusco <ffusco@...hat.com>
Date: Tue, 24 Sep 2013 15:43:07 +0200

> There is no way to set the IP_TOS field on a per-packet basis in IPv4, while
> IPv6 has such a mechanism. Therefore one has to fall back to the setsockopt()
> in case of IPv4. 
> 
> Using the existing per-socket option is not convenient particularly in the
> situations where multiple threads have to use the same socket data requiring
> per-thread TOS values. In fact this would involve calling setsockopt() before
> sendmsg() every time.

Series applied, thank you.
--
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