Date: Sun, 23 Sep 2007 15:47:13 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Darren Reed" <darrenr@freebsd.org> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, Jack Vogel <jfvogel@gmail.com> Subject: Re: TX Multiqueue? Message-ID: <b1fa29170709231547w26f84901s92c6f63baf829269@mail.gmail.com> In-Reply-To: <46F614F2.4050402@freebsd.org> References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <b1fa29170709221701m3c13cddakd83c9550905b8bd8@mail.gmail.com> <46F614F2.4050402@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/23/07, Darren Reed <darrenr@freebsd.org> wrote: > Kip Macy wrote: > > My ethng branch supports multiple rx and tx queues. > > > > -Kip > > > > What are your plans for how we use/manage/interact with the mutiple > rx/tx queues? The rx hardware queue is determined by the hardware. Different hardware allows for different policies. I just use the stock rss_hash of a crc32 of the 4-tuple in cxgb. I've added a field to the pkthdr which cxgb uses the least significant bits of to determine which outbound queue to use. Its up to the upper layers to determine how to set those bits. One of the changes that is required to take advantaged of this is moving the queues into the driver. I've added a new if_start function to ifnet to take advantage of this. I also have a normal if_start function for backward compatibility. -Kip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170709231547w26f84901s92c6f63baf829269>