Date: Fri, 07 Sep 2012 13:45:43 -0400 From: gnn@freebsd.org To: Anuranjan Shukla <anshukla@juniper.net> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org> Subject: Re: Proposal for changes to network device drivers and network stack (RFC) Message-ID: <86har9iv5k.wl%gnn@neville-neil.com> In-Reply-To: <CC6EF6B2.1917A%anshukla@juniper.net> References: <5F3C03B6-01D0-42DE-BE9E-323DBDC90C8E@neville-neil.com> <CC6EF6B2.1917A%anshukla@juniper.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At Fri, 7 Sep 2012 01:28:16 -0700,
Anuranjan Shukla wrote:
>
>
> >
> >> struct socket {
> >>
> >> int so_fibnum; /* routing domain for this socket */
> >> uint32_t so_user_cookie;
> >> + u_int so_oqueue; /* manage send prioritizing based on
> >>application
> >> needs */
> >> + u_short so_lrid; /* logical routing */
> >> };
> >>
> >
> >I'd be interested to know how this is used.
>
> We use the first one as a 'direction' to the forwarding path to select an
> appropriate priority queue to send the packet on. In a generic (i.e.
> Something other than our specific system) system, one could consider
> interesting ways to use queues on a multi queue NIC with help from a
> driver. The second one is for a system with logical routing capabilities
> (multiple routing systems within the same chassis). It gives an
> application opening a socket an option to select the specific logical
> routing instance.
OK, that's what I guessed but thanks for confirming it.
> I'll provide smaller pieces of diffs for the kernel without networking
> patch I'd sent out. Let me know if you prefer the device driver interface
> to be in that too.
Yes, please.
Best,
George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86har9iv5k.wl%gnn>