From: Neil Horman <nhorman@tuxdriver.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: John Fastabend <john.r.fastabend@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Andy Gospodarek <andy@greyhouse.net>,
netdev <netdev@vger.kernel.org>
Subject: Re: Layer 2 acceleration vs GSO
Date: Fri, 10 Jan 2014 15:32:22 -0500 [thread overview]
Message-ID: <20140110203222.GB2645@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1389384339.2025.88.camel@bwh-desktop.uk.level5networks.com>
On Fri, Jan 10, 2014 at 08:05:39PM +0000, Ben Hutchings wrote:
> What happens when an skb to be sent through ndo_dfwd_start_xmit()
> requires software GSO?
>
> dev_hard_start_xmit() will segment it and then submit each segment, and
> then:
>
> > gso:
> > do {
> [...]
> > if (accel_priv)
> > rc = ops->ndo_dfwd_start_xmit(nskb, dev, accel_priv);
> > else
> > rc = ops->ndo_start_xmit(nskb, dev);
> > trace_net_dev_xmit(nskb, rc, dev, skb_len);
> [...]
> > txq_trans_update(txq);
>
> Oops, txq is NULL. And once we add the obvious condition to that,
>
> > if (unlikely(netif_xmit_stopped(txq) && skb->next))
> > return NETDEV_TX_BUSY;
>
> How can we tell if the hardware transmit queue filled up?
>
> It seems like this feature currently relies on the driver returning
> NETDEV_TX_BUSY when the TX queue is already full, like ixgbe does. But
> that is exactly what drivers are *not* supposed to do.
>
> Ben.
>
> > } while (skb->next);
>
Dave just to a fix to deal with this (among some other issues) here today:
http://marc.info/?l=linux-kernel&m=138934276507518&w=2
Neil
> --
> Ben Hutchings, Staff Engineer, Solarflare
> Not speaking for my employer; that's the marketing department's job.
> They asked us to note that Solarflare product names are trademarked.
>
>
next prev parent reply other threads:[~2014-01-10 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 20:05 Layer 2 acceleration vs GSO Ben Hutchings
2014-01-10 20:32 ` Neil Horman [this message]
2014-01-10 20:39 ` Ben Hutchings
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140110203222.GB2645@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=andy@greyhouse.net \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox