From: Eric Dumazet <eric.dumazet@gmail.com>
To: igorm@etf.rs
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next] r8169: Support for byte queue limits
Date: Fri, 16 Dec 2011 22:30:03 +0100 [thread overview]
Message-ID: <1324071003.2621.33.camel@edumazet-laptop> (raw)
In-Reply-To: <1323694834-2844-1-git-send-email-igorm@etf.rs>
Le lundi 12 décembre 2011 à 05:00 -0800, igorm@etf.rs a écrit :
> From: Igor Maravic <igorm@etf.rs>
>
> Changes to r8169 to use byte queue limits.
>
> Signed-off-by: Igor Maravic <igorm@etf.rs>
> Signed-off-by: Igor Maravić <igorm@etf.rs>
Dont forget to CC maintainer of this driver.
> ---
> drivers/net/ethernet/realtek/r8169.c | 13 +++++++++++--
> 1 files changed, 11 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
> index 36b2a4b..bfdb5fd 100644
> --- a/drivers/net/ethernet/realtek/r8169.c
> +++ b/drivers/net/ethernet/realtek/r8169.c
> @@ -5326,6 +5326,7 @@ static void rtl8169_tx_clear(struct rtl8169_private *tp)
> {
> rtl8169_tx_clear_range(tp, tp->dirty_tx, NUM_TX_DESC);
> tp->cur_tx = tp->dirty_tx = 0;
> + netdev_reset_queue(tp->dev);
> }
>
> static void rtl8169_schedule_work(struct net_device *dev, work_func_t task)
> @@ -5460,6 +5461,8 @@ static int rtl8169_xmit_frags(struct rtl8169_private *tp, struct sk_buff *skb,
> txd->opts1 |= cpu_to_le32(LastFrag);
> }
>
> + netdev_sent_queue(tp->dev, skb->len);
> +
Why here in rtl8169_xmit_frags() ?
If done from rtl8169_start_xmit(), you already have "dev" pointer.
netdev_sent_queue(dev, skb->len);
next prev parent reply other threads:[~2011-12-16 21:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-12 13:00 [PATCH net-next] r8169: Support for byte queue limits igorm
2011-12-16 21:15 ` David Miller
2011-12-16 21:30 ` Eric Dumazet [this message]
2011-12-17 17:28 ` Igor Maravić
-- strict thread matches above, loose matches on Subject: below --
2011-12-19 10:28 igorm
2011-12-19 19:18 ` David Miller
2011-12-19 10:09 igorm
2011-12-19 10:19 ` Eric Dumazet
2011-12-19 9:27 igorm
2011-12-19 9:29 ` Igor Maravić
2011-12-19 9:46 ` Eric Dumazet
2011-12-19 9:53 ` Igor Maravić
2011-12-06 9:13 igorm
2011-12-06 9:15 ` Igor Maravić
2011-12-06 18:13 ` David Miller
2011-12-06 21:36 ` Igor Maravić
2011-12-06 21:41 ` David Miller
2011-12-02 13:09 igorm
2011-12-02 14:29 ` Eric Dumazet
2011-12-02 14:54 ` Igor Maravić
2011-12-02 15:11 ` Eric Dumazet
2011-12-02 16:31 ` "Igor Maravić"
2011-12-02 16:47 ` Eric Dumazet
2011-12-02 17:00 ` Igor Maravić
2011-12-02 17:12 ` Eric Dumazet
2011-12-02 21:54 ` Igor Maravić
2011-12-03 6:48 ` Eric Dumazet
2011-12-03 0:20 ` Francois Romieu
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=1324071003.2621.33.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=igorm@etf.rs \
--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