From: Ivan Vecera <ivecera@redhat.com> Date: 2016-08-30 14:38:59
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(+)
From: Michael Chan <michael.chan@broadcom.com> Date: 2016-08-30 15:46:09
On Tue, Aug 30, 2016 at 7:38 AM, Ivan Vecera [off-list ref] wrote:
quoted hunk
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(+)
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;
From: Sergei Shtylyov <hidden> Date: 2016-08-30 17:53:01
Hello.
On 08/30/2016 05:38 PM, Ivan Vecera wrote:
The recent commit 087d7a8c disallows to set Rx coalescing time to be 0
You should specify both 12-digit SHA1 and the commit summary enclosed in ("").
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>
From: Ivan Vecera <ivecera@redhat.com> Date: 2016-08-31 09:26:00
Dne 30.8.2016 v 19:52 Sergei Shtylyov napsal(a):
Hello.
On 08/30/2016 05:38 PM, Ivan Vecera wrote:
quoted
The recent commit 087d7a8c disallows to set Rx coalescing time to be 0
You should specify both 12-digit SHA1 and the commit summary enclosed in ("").
quoted
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>
From: Ivan Vecera <ivecera@redhat.com> Date: 2016-08-31 09:27:05
Dne 30.8.2016 v 17:46 Michael Chan napsal(a):
On Tue, Aug 30, 2016 at 7:38 AM, Ivan Vecera [off-list ref] wrote:
quoted
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(+)
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?
Ivan
From: Michael Chan <michael.chan@broadcom.com> Date: 2016-08-31 16:19:49
On Wed, Aug 31, 2016 at 2:27 AM, Ivan Vecera [off-list ref] wrote:
Dne 30.8.2016 v 17:46 Michael Chan napsal(a):
quoted
On Tue, Aug 30, 2016 at 7:38 AM, Ivan Vecera [off-list ref] wrote:
quoted
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
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.
From: Ivan Vecera <ivecera@redhat.com> Date: 2016-09-01 09:29:26
Dne 31.8.2016 v 18:19 Michael Chan napsal(a):
On Wed, Aug 31, 2016 at 2:27 AM, Ivan Vecera [off-list ref] wrote:
quoted
Dne 30.8.2016 v 17:46 Michael Chan napsal(a):
quoted
On Tue, Aug 30, 2016 at 7:38 AM, Ivan Vecera [off-list ref] wrote:
quoted
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
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.