Date: Tue, 04 Mar 2014 19:14:02 +0700 From: Eugene Grosbein <egrosbein@rdtc.ru> To: Adrian Chadd <adrian.chadd@gmail.com> Cc: FreeBSD Net <freebsd-net@freebsd.org>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: UDP transmit and no flowid Message-ID: <5315C38A.1010508@rdtc.ru> In-Reply-To: <CAJ-VmomNsR5n8K7k%2BqcTAaAn0HiUcxmFVDxJUw8AD5ZyKHTn5w@mail.gmail.com> References: <CAJ-VmomNsR5n8K7k%2BqcTAaAn0HiUcxmFVDxJUw8AD5ZyKHTn5w@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 04.03.2014 08:17, Adrian Chadd wrote: > I'll try this out in the next week or two once I've sorted out my > employment situation and I can reserve some time on the netperf > cluster. There is a patch written by melifaro@freebsd.org to introduce IP flow id generation and modified by me to add sysctl net.inet.ip.skip_flowid_gen to disable id generation in run time and return pre-patched behavior: http://www.grosbein.net/freebsd/patches/netisr_ip_flowid.diff I've tested it in production for mpd5-based high loaded BRAS, it works just fine. It uses IP src/dst addresses and TCP/UDP/SCTP ports to feed jenkins_hashword() and to fill m->m_pkthdr.flowid. Eugene Grosbein.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5315C38A.1010508>