netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivan Vecera <ivecera@redhat.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: Netdev <netdev@vger.kernel.org>,
	Satish Baddipadige <satish.baddipadige@broadcom.com>,
	Siva Reddy Kallam <siva.kallam@broadcom.com>
Subject: Re: [PATCH net] tg3: Fix for disallow tx coalescing time to be 0
Date: Thu, 1 Sep 2016 11:29:23 +0200	[thread overview]
Message-ID: <12380da3-2dc1-5cd5-b8d9-e4384a62f4e4@redhat.com> (raw)
In-Reply-To: <CACKFLinmEkScvrsVX-R5e+8UjNvNzRhbwtH1pCDFZjkhTMxsxA@mail.gmail.com>

Dne 31.8.2016 v 18:19 Michael Chan napsal(a):
> On Wed, Aug 31, 2016 at 2:27 AM, Ivan Vecera <ivecera@redhat.com> wrote:
>> Dne 30.8.2016 v 17:46 Michael Chan napsal(a):
>>>
>>> On Tue, Aug 30, 2016 at 7:38 AM, Ivan Vecera <ivecera@redhat.com> wrote:
>>>>
>>>> The recent commit 087d7a8c disallows to set Rx coalescing time to be 0
>>>> as this stops generating interrupts for the incoming packets. I found
>>>> the zero Tx coalescing time stops generating interrupts similarly for
>>>> outgoing packets and fires Tx watchdog later. To avoid this, don't allow
>>>> to set Tx coalescing time to 0.
>>>>
>>>> Cc: satish.baddipadige@broadcom.com
>>>> Cc: siva.kallam@broadcom.com
>>>> Cc: michael.chan@broadcom.com
>>>> Signed-off-by: Ivan Vecera <ivecera@redhat.com>
>>>> ---
>>>>  drivers/net/ethernet/broadcom/tg3.c | 1 +
>>>>  1 file changed, 1 insertion(+)
>>>>
>>>> diff --git a/drivers/net/ethernet/broadcom/tg3.c
>>>> b/drivers/net/ethernet/broadcom/tg3.c
>>>> index 6592612..07e3beb 100644
>>>> --- a/drivers/net/ethernet/broadcom/tg3.c
>>>> +++ b/drivers/net/ethernet/broadcom/tg3.c
>>>> @@ -14012,6 +14012,7 @@ static int tg3_set_coalesce(struct net_device
>>>> *dev, struct ethtool_coalesce *ec)
>>>>         if ((ec->rx_coalesce_usecs > MAX_RXCOL_TICKS) ||
>>>>             (!ec->rx_coalesce_usecs) ||
>>>>             (ec->tx_coalesce_usecs > MAX_TXCOL_TICKS) ||
>>>> +           (!ec->tx_coalesce_usecs) ||
>>>>             (ec->rx_max_coalesced_frames > MAX_RXMAX_FRAMES) ||
>>>>             (ec->tx_max_coalesced_frames > MAX_TXMAX_FRAMES) ||
>>>>             (ec->rx_coalesce_usecs_irq > max_rxcoal_tick_int) ||
>>>
>>>
>>>
>>> As Rick pointed out last time, we can remove this check which follows
>>> the block of code above:
>>>
>>> /* No tx interrupts will be generated if both are zero */
>>> if ((ec->tx_coalesce_usecs == 0) &&
>>>    (ec->tx_max_coalesced_frames == 0))
>>> return -EINVAL;
>>>
>> Michael,
>> should I add the removal of these checks to v2?
>>
> Yes, please remove both the TX and the RX checks.  Thanks.
>
Ok, v2 sent.

I.

  reply	other threads:[~2016-09-01  9:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-30 14:38 [PATCH net] tg3: Fix for disallow tx coalescing time to be 0 Ivan Vecera
2016-08-30 15:46 ` Michael Chan
2016-08-31  9:27   ` Ivan Vecera
2016-08-31 16:19     ` Michael Chan
2016-09-01  9:29       ` Ivan Vecera [this message]
2016-08-30 17:52 ` Sergei Shtylyov
2016-08-31  9:25   ` Ivan Vecera

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=12380da3-2dc1-5cd5-b8d9-e4384a62f4e4@redhat.com \
    --to=ivecera@redhat.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=satish.baddipadige@broadcom.com \
    --cc=siva.kallam@broadcom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).