netdev - Re: [RFC] tcp: add support for scheduling TCP options on TCP sockets

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20140507.132301.170284205486641795.davem@davemloft.net>
Date:	Wed, 07 May 2014 13:23:01 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	christoph.paasch@...ouvain.be
Cc:	octavian.purdila@...el.com, netdev@...r.kernel.org
Subject: Re: [RFC] tcp: add support for scheduling TCP options on TCP
 sockets

From: Christoph Paasch <christoph.paasch@...ouvain.be>
Date: Wed, 7 May 2014 16:11:08 +0200

> Yes, but it could be done in a more "clean" way so that future
> extensions to TCP are no more limited by the limitation of struct
> tcp_skb_cb.

Would you stop harping on this point?

Adding new options to TCP is a really big deal, it implicitly
involves deeply understanding how it interacts with other options
and what is the most optimal way to insert those options in the
output path.

It should be "hard".
--
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