> PJ Waskiewicz wrote:
> > diff --git a/include/linux/skbuff.h b/include/linux/skbuff.h index
> > e7367c7..8bcd870 100644
> > --- a/include/linux/skbuff.h
> > +++ b/include/linux/skbuff.h
> > @@ -215,6 +215,7 @@ typedef unsigned char *sk_buff_data_t;
> > * @pkt_type: Packet class
> > * @fclone: skbuff clone status
> > * @ip_summed: Driver fed us an IP checksum
> > + * @queue_mapping: Queue mapping for multiqueue devices
> > * @priority: Packet queueing priority
> > * @users: User count - see {datagram,tcp}.c
> > * @protocol: Packet protocol from driver
> > @@ -269,6 +270,7 @@ struct sk_buff {
> > __u16 csum_offset;
> > };
> > };
> > + __u16 queue_mapping;
> > __u32 priority;
> > __u8 local_df:1,
> > cloned:1,
>
>
> I think we can reuse skb->priority. Assuming only real
> hardware devices use multiqueue support, there should be no user of
> skb->priority after egress qdisc classification. The only reason
> to preserve it in the qdisc layer is for software devices.
That would be oustanding.
> Grepping through drivers/net shows a few users, bot most seem
> to be using it on the RX path and some use it to store internal data.
Thank you for hunting this down. I will test on my little environment
here to see if I run into any issues.
-PJ
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
