diff options
| author | David Gibson <david@gibson.dropbear.id.au> | 2023-09-28 11:21:02 +1000 |
|---|---|---|
| committer | Stefano Brivio <sbrivio@redhat.com> | 2023-09-30 12:40:53 +0200 |
| commit | fc8f0f8c48ef12edbf60f74f37024917f5812385 (patch) | |
| tree | 470cc57b733611a8447b725635fa5d9e18b7315d /Makefile | |
| parent | 04b10a8d907d8ceb09e3adb4885c02f546841bbc (diff) | |
| download | passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar.gz passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar.bz2 passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar.lz passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar.xz passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.tar.zst passt-fc8f0f8c48ef12edbf60f74f37024917f5812385.zip | |
siphash: Use incremental rather than all-at-once siphash functions
We have a bunch of variants of the siphash functions for different data
sizes. The callers, in tcp.c, need to pack the various values they want to
hash into a temporary structure, then call the appropriate version. We can
avoid the copy into the temporary by directly using the incremental
siphash functions.
The length specific hash functions also have an undocumented constraint
that the data pointer they take must, in fact, be aligned to avoid
unaligned accesses, which may cause crashes on some architectures.
So, prefer the incremental approach and remove the length-specific
functions.
Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Diffstat (limited to 'Makefile')
| -rw-r--r-- | Makefile | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -45,7 +45,7 @@ FLAGS += -DDUAL_STACK_SOCKETS=$(DUAL_STACK_SOCKETS) PASST_SRCS = arch.c arp.c checksum.c conf.c dhcp.c dhcpv6.c icmp.c igmp.c \ isolation.c lineread.c log.c mld.c ndp.c netlink.c packet.c passt.c \ - pasta.c pcap.c siphash.c tap.c tcp.c tcp_splice.c udp.c util.c + pasta.c pcap.c tap.c tcp.c tcp_splice.c udp.c util.c QRAP_SRCS = qrap.c SRCS = $(PASST_SRCS) $(QRAP_SRCS) |