[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <OFD4E8C537.53B7FE22-ON652572DE.001ABA41-652572DE.001BA4ED@in.ibm.com>
Date: Thu, 17 May 2007 10:31:56 +0530
From: Krishna Kumar2 <krkumar2@...ibm.com>
To: Sridhar Samudrala <sri@...ibm.com>
Cc: ak@...e.de, ashwin.chaugule@...unite.com,
David Miller <davem@...emloft.net>,
Gagan Arneja <gagan@...are.com>, hadi@...erus.ca,
Evgeniy Polyakov <johnpol@....mipt.ru>, netdev@...r.kernel.org,
netdev-owner@...r.kernel.org, rdreier@...co.com, xma@...ibm.com
Subject: Re: [WIP] [PATCH] WAS Re: [RFC] New driver API to speed up small packets
xmits
Sridhar Samudrala <sri@...ibm.com> wrote on 05/17/2007 03:14:41 AM:
> Krishna Kumar2 wrote:
> > Hi Sridhar,
> >
> > Sridhar Samudrala <sri@...ibm.com> wrote on 05/17/2007 03:42:03 AM:
> >
> >> AFAIK, gso_skb can be a list of skb's. Can we add a list
> >> to another list using __skb_queue_head()?
> >> Also, if gso_skb is a list of multiple skb's, i think the
> >> count needs to be decremented by the number of segments in
> >> gso_skb.
> >
> > gso_skb is the last GSO skb that failed to be sent. This already
> > segmented skb is kept "cached" and whenever the next xmit happens,
> > this skb is first sent before any packets from the queue are taken
> > out (otherwise out-of-order packets). So there can atmost be one
> > gso_skb per device.
>
> Yes. There can be only one gso_skb per device. But it can have more
> than one segments linked together via skb->next.
It will definitely have more than 1 segments (criterea to be on the
gso_skb). But I think you are right, the segmented skb will "lose"
it's 1-n segments (newsk->next = next) when it is added to the list.
Thanks,
- KK
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists