netdev - RE: [PATCH net] sctp: support global vtag assochash and per endpoint s(d)port assochash table

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: <063D6719AE5E284EB5DD2968C1650D6D1CB8B410@AcuExch.aculab.com>
Date:	Tue, 1 Sep 2015 14:53:38 +0000
From:	David Laight <David.Laight@...LAB.COM>
To:	'Xin Long' <lucien.xin@...il.com>,
	network dev <netdev@...r.kernel.org>
CC:	"mleitner@...hat.com" <mleitner@...hat.com>,
	"vyasevic@...hat.com" <vyasevic@...hat.com>,
	"daniel@...earbox.net" <daniel@...earbox.net>,
	"davem@...emloft.net" <davem@...emloft.net>
Subject: RE: [PATCH net] sctp: support global vtag assochash and per
 endpoint s(d)port assochash table

From: Xin Long
> Sent: 31 August 2015 18:44
>
> for telecom center, the usual case is that a server is connected by thousands
> of clients. but if the server with only one enpoint(udp style) use the same
> sport and dport to communicate with every clients, and every assoc in server
> will be hashed in the same chain of global assoc hashtable due to currently we
> choose dport and sport as the hash key.

I'm not sure the above is true...

Although a server might be connected to 1000s of clients, if the sctp
'application' is M3UA then it is very likely that the source and
destination ports for all the associations are all the same (2905).

An M3UA application might also be written to use a single socket
(eg: in order to reduce the number of fds and/or poll() list size).

	David

--
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