Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Jul 2007 16:53:36 -0700
From:      "Kip Macy" <kip.macy@gmail.com>
To:        "Alexey Karagodov" <karagodov@gmail.com>
Cc:        FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject:   Re: call for ALTQ users
Message-ID:  <b1fa29170707281653v35eab694s8ebcf61e4d7b86ea@mail.gmail.com>
In-Reply-To: <c7aff4ef0707281650q542b8640rdd5ca1284b4fef60@mail.gmail.com>
References:  <b1fa29170707281403t37de71basf50a5d437e24bf22@mail.gmail.com> <b1fa29170707281438w4527bcffnd3addef26fc4d933@mail.gmail.com> <c7aff4ef0707281650q542b8640rdd5ca1284b4fef60@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 7/28/07, Alexey Karagodov <karagodov@gmail.com> wrote:
> how can i help you?

I'd like to understand how ALTQ is being used currently. Are there
users using it on high bandwidth interfaces?

As currently implemented it would force serialization, increased
locking overhead, and potentially loss of locality on cards that
support multiple queues (i.e. most 10GigE cards).

     -Kip

>
> 2007/7/29, Kip Macy <kip.macy@gmail.com>:
> >
> > Expanding the net a bit.
> >
> > ---------- Forwarded message ----------
> > From: Kip Macy <kip.macy@gmail.com>
> > Date: Jul 28, 2007 2:03 PM
> > Subject: call for ALTQ users
> > To: freebsd-net <freebsd-net@freebsd.org>
> >
> >
> > I'm looking at extending ifnet to support multiple tx queues. It
> > appears that this will inevitably interact with ALTQ. I don't know
> > anyone using ALTQ so I need users to raise their hands to eventually
> > test prospective changes.
> >
> > Thanks.
> >
> >        -Kip
> > _______________________________________________
> > 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?b1fa29170707281653v35eab694s8ebcf61e4d7b86ea>