RE: [PATCH v2 0/2] net: thunderx: Support for pass-2 hw features

From: Pavel Fedin
Date: Thu Dec 10 2015 - 03:52:25 EST


All series:

Reviewed-by: Pavel Fedin <p.fedin@xxxxxxxxxxx>

Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia

-----Original Message-----
From: netdev-owner@xxxxxxxxxxxxxxx [mailto:netdev-owner@xxxxxxxxxxxxxxx] On Behalf Of Sunil Goutham
Sent: Thursday, December 10, 2015 10:55 AM
To: netdev@xxxxxxxxxxxxxxx
Cc: linux-kernel@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; p.fedin@xxxxxxxxxxx; Sunil.Goutham@xxxxxxxxxxxxxxxxxx; Sunil
Goutham
Subject: [PATCH v2 0/2] net: thunderx: Support for pass-2 hw features

From: Sunil Goutham <sgoutham@xxxxxxxxxx>

This patch set adds support for new features added in pass-2 revision of hardware like TSO and count based interrupt coalescing.

Changes from v1:
- Addressed comments received regarding boolean bit field changes
by excluding them from this patch. Will submit a seperate
patch along with cleanup of unsed field.
- Got rid of new macro 'VNIC_NAPI_WEIGHT' introduced in
count threshold interrupt patch.

Sunil Goutham (2):
net: thunderx: HW TSO support for pass-2 hardware
net: thunderx: Enable CQE count threshold interrupt

drivers/net/ethernet/cavium/thunder/nic.h | 6 ++++
drivers/net/ethernet/cavium/thunder/nic_main.c | 11 ++-----
drivers/net/ethernet/cavium/thunder/nicvf_main.c | 15 ++++++++-
drivers/net/ethernet/cavium/thunder/nicvf_queues.c | 22 ++++++++++----
drivers/net/ethernet/cavium/thunder/nicvf_queues.h | 2 +-
drivers/net/ethernet/cavium/thunder/q_struct.h | 30 ++++++++++---------
6 files changed, 55 insertions(+), 31 deletions(-)

--
To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@xxxxxxxxxxxxxxx More
majordomo info at http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/