All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Tino Reichardt <milky-kernel@mcmilk.de>,
	netdev@vger.kernel.org,
	Realtek linux nic maintainers <nic_swsd@realtek.com>,
	Igor Maravic <igorm@etf.rs>,
	Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [PATCH net-next v3 02/07] r8169: Support for byte queue limits
Date: Mon, 21 Oct 2013 17:38:00 +0400	[thread overview]
Message-ID: <52652E38.5020207@cogentembedded.com> (raw)
In-Reply-To: <1382296991-20289-3-git-send-email-milky-kernel@mcmilk.de>

Hello.

On 10/20/2013 11:23 PM, Tino Reichardt wrote:

> Changes to r8169 driver to use byte queue limits.


> Signed-off-by: Tino Reichardt <milky-kernel@mcmilk.de>

> ---
>   drivers/net/ethernet/realtek/r8169.c | 14 ++++++++++++++
>   1 file changed, 14 insertions(+)

> diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
> index 3397cee..8f12145 100644
> --- a/drivers/net/ethernet/realtek/r8169.c
> +++ b/drivers/net/ethernet/realtek/r8169.c
[...]
> @@ -818,6 +819,9 @@ MODULE_AUTHOR("Realtek and the Linux r8169 crew <netdev@vger.kernel.org>");
>   MODULE_DESCRIPTION("RealTek RTL-8169 Gigabit Ethernet driver");
>   module_param(use_dac, int, 0);
>   MODULE_PARM_DESC(use_dac, "Enable PCI DAC. Unsafe on 32 bit PCI slot.");
> +module_param(bql_disable, bool, 0);
> +MODULE_PARM_DESC(bql_disable,
> +	"Disable Byte Queue Limits functionality (default: false)");
>   module_param_named(debug, debug.msg_enable, int, 0);
>   MODULE_PARM_DESC(debug, "Debug verbosity level (0=none, ..., 16=all)");
>   MODULE_LICENSE("GPL");
> @@ -5841,6 +5845,8 @@ 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;
> +	if (unlikely(bql_disable))
> +		netdev_reset_queue(tp->dev);

    Joe has inverted the logic in his request and you blindly followed it. He 
must have meant !bql_disable. Also, unlikely() does not really fit here, so in 
fact Joe's request was completely invalid.

WBR, Sergei

  parent reply	other threads:[~2013-10-21 13:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-20 19:23 [PATCHSET net-next v3 00/07] Support for byte queue limits on various drivers Tino Reichardt
2013-10-20 19:23 ` [PATCH net-next v3 01/07] 8139too: Support for byte queue limits Tino Reichardt
2013-10-20 19:23 ` [PATCH net-next v3 02/07] r8169: " Tino Reichardt
2013-10-21  9:55   ` Ben Hutchings
2013-10-21 13:38   ` Sergei Shtylyov [this message]
2013-10-20 19:23 ` [PATCH net-next v3 03/07] tulip: " Tino Reichardt
2013-10-21  3:00   ` Grant Grundler
2013-10-20 19:23 ` [PATCH net-next v3 04/07] via-rhine: " Tino Reichardt
2013-10-20 19:23 ` [PATCH net-next v3 05/07] via-velocity: " Tino Reichardt
2013-10-20 19:23 ` [PATCH net-next v3 06/07] 3c59x: " Tino Reichardt
2013-10-20 19:23 ` [PATCH net-next v3 07/07] natsemi: " Tino Reichardt
2013-10-20 19:38 ` [PATCHSET net-next v3 00/07] Support for byte queue limits on various drivers Joe Perches
2013-10-20 20:19 ` Tino Reichardt
2013-10-20 21:13 ` Andi Kleen
2013-10-21  9:53   ` Ben Hutchings
2013-10-20 22:07 ` 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=52652E38.5020207@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=igorm@etf.rs \
    --cc=milky-kernel@mcmilk.de \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=romieu@fr.zoreil.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.