Date: Sun, 23 Sep 2007 00:25:38 -0700 From: Darren Reed <darrenr@freebsd.org> To: Kip Macy <kip.macy@gmail.com> 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: <46F614F2.4050402@freebsd.org> In-Reply-To: <b1fa29170709221701m3c13cddakd83c9550905b8bd8@mail.gmail.com> References: <2a41acea0709221656n4aa62776y488c7f2da262c9f6@mail.gmail.com> <b1fa29170709221701m3c13cddakd83c9550905b8bd8@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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? Darren > On 9/22/07, Jack Vogel <jfvogel@gmail.com> wrote: > > Our newest E1000 nic, the 82575, and the Oplin 10G hardware are capable of > > multiple queues both on the receive and the send side. On the receive end for > > the Oplin driver the queues actually help distribute interrupts and improve > > performance without any special support in the stack. > > > > I have been asked about multiple queues on the TX side, embedded appliance > > type system builders for instance are interested I suppose for > > priority queueing. > > Is anyone working on this right now, and if not does this sound like something > > anyone is interested in doing? > > > > I would like to see MQ on both TX and RX that drivers could use if able. > > > > Jack > > _______________________________________________ > > freebsd-net@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-net > > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?46F614F2.4050402>