From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, David Miller <davem@davemloft.net>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Gregory Clement <gregory.clement@free-electrons.com>,
Lior Amsalem <alior@marvell.com>,
Tawfik Bayouk <tawfik@marvell.com>,
fugang.duan@freescale.com, Willy Tarreau <w@1wt.eu>
Subject: Re: [PATCH 6/8] net: mv643xx_eth: Limit the TSO segments and adjust stop/wake thresholds
Date: Fri, 30 May 2014 15:08:39 -0300 [thread overview]
Message-ID: <20140530180839.GA12172@arch.cereza> (raw)
In-Reply-To: <1401470493.3645.129.camel@edumazet-glaptop2.roam.corp.google.com>
Hi Eric,
On 30 May 10:21 AM, Eric Dumazet wrote:
> On Fri, 2014-05-30 at 13:40 -0300, Ezequiel Garcia wrote:
> >
> > -static int txq_submit_skb(struct tx_queue *txq, struct sk_buff *skb)
> > +static int txq_submit_skb(struct tx_queue *txq, struct sk_buff *skb,
> > + struct net_device *dev)
> > {
> > struct mv643xx_eth_private *mp = txq_to_mp(txq);
> > int nr_frags = skb_shinfo(skb)->nr_frags;
> > @@ -910,11 +918,15 @@ static int txq_submit_skb(struct tx_queue *txq, struct sk_buff *skb)
> > cmd_sts = 0;
> > l4i_chk = 0;
> >
> > + if (txq->tx_ring_size - txq->tx_desc_count < MAX_SKB_FRAGS + 1) {
>
> I am not sure I understand this part.
>
> You have one skb here, so why are you using MAX_SKB_FRAGS ?
>
This check was moved around, so I'm blindly carrying it over.
You meant that I can directly use skb_shinfo(skb)->nr_frags, right?
> > + if (net_ratelimit())
> > + netdev_err(dev, "tx queue full?!\n");
> > + return -EBUSY;
> > + }
> > +
>
> Also it looks like this part will become dead after the following
> patch...
>
Indeed, I've kept it just for consistency. I had to return some error value
and EBUSY seems the most appropriate. Do you think I should change this?
Thanks for the feedback,
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-05-30 18:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-30 16:40 [PATCH 0/8] ethernet: marvell: After-TSO fixes Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 1/8] net: mvneta: Use default NAPI weight instead of a custom one Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 2/8] net: mvneta: Limit the TSO segments and adjust stop/wake thresholds Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 3/8] net: mvneta: Fix missing DMA region unmap Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 4/8] net: mvneta: Avoid unmapping the TSO header buffers Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 5/8] net: mv643xx_eth: Count dropped packets properly Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 6/8] net: mv643xx_eth: Limit the TSO segments and adjust stop/wake thresholds Ezequiel Garcia
2014-05-30 17:21 ` Eric Dumazet
2014-05-30 18:08 ` Ezequiel Garcia [this message]
2014-05-30 16:40 ` [PATCH 7/8] net: mv643xx_eth: Drop the NETDEV_TX_BUSY return path Ezequiel Garcia
2014-05-30 16:40 ` [PATCH 8/8] net: mv643xx_eth: Avoid unmapping the TSO header buffers Ezequiel Garcia
2014-06-02 23:16 ` [PATCH 0/8] ethernet: marvell: After-TSO fixes David Miller
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=20140530180839.GA12172@arch.cereza \
--to=ezequiel.garcia@free-electrons.com \
--cc=alior@marvell.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fugang.duan@freescale.com \
--cc=gregory.clement@free-electrons.com \
--cc=netdev@vger.kernel.org \
--cc=tawfik@marvell.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=w@1wt.eu \
/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