mbox series

[net-next,v3,0/6] ravb: Align Rx descriptor setup and maintenance

Message ID 20240304110858.117100-1-niklas.soderlund+renesas@ragnatech.se (mailing list archive)
Headers show
Series ravb: Align Rx descriptor setup and maintenance | expand

Message

Niklas Söderlund March 4, 2024, 11:08 a.m. UTC
Hello,

When RZ/G2L support was added the Rx code path was split in two, one to
support R-Car and one to support RZ/G2L. One reason for this is that
R-Car uses the extended Rx descriptor format, while RZ/G2L uses the
normal descriptor format.

In many aspects this is not needed as the extended descriptor format is
just a normal descriptor with extra metadata (timestamsp) appended. And
the R-Car SoCs can also use normal descriptors if hardware timestamps
were not desired. This split has led to RZ/G2L gaining support for
split descriptors in the Rx path while R-Car still lacks this.

This series is the first step in trying to merge the R-Car and RZ/G2L Rx
paths so features and bugs corrected in one will benefit the other.

The first patch in the series clarifies that the driver now supports
either normal or extended descriptors, not both at the same time by
grouping them in a union. This is the foundation that later patches will
build on the aligning the two Rx paths.

Patches 2-5 deals with correcting small issues in the Rx frame and
descriptor sizes that either were incorrect at the time they were added
in 2017 (my bad) or concepts built on-top of this initial incorrect
design.

While finally patch 6 merges the R-Car and RZ/G2L for Rx descriptor
setup and maintenance.

When this work has landed I plan to follow up with more work aligning
the rest of the Rx code paths and hopefully bring split descriptor
support to the R-Car SoCs.

Niklas Söderlund (6):
  ravb: Group descriptor types used in Rx ring
  ravb: Make it clear the information relates to maximum frame size
  ravb: Create helper to allocate skb and align it
  ravb: Use the max frame size from hardware info for RZ/G2L
  ravb: Move maximum Rx descriptor data usage to info struct
  ravb: Unify Rx ring maintenance code paths

 drivers/net/ethernet/renesas/ravb.h      |  20 +--
 drivers/net/ethernet/renesas/ravb_main.c | 210 ++++++++---------------
 2 files changed, 83 insertions(+), 147 deletions(-)

Comments

patchwork-bot+netdevbpf@kernel.org March 6, 2024, 11:30 a.m. UTC | #1
Hello:

This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:

On Mon,  4 Mar 2024 12:08:52 +0100 you wrote:
> Hello,
> 
> When RZ/G2L support was added the Rx code path was split in two, one to
> support R-Car and one to support RZ/G2L. One reason for this is that
> R-Car uses the extended Rx descriptor format, while RZ/G2L uses the
> normal descriptor format.
> 
> [...]

Here is the summary with links:
  - [net-next,v3,1/6] ravb: Group descriptor types used in Rx ring
    https://git.kernel.org/netdev/net-next/c/4123c3fbf863
  - [net-next,v3,2/6] ravb: Make it clear the information relates to maximum frame size
    https://git.kernel.org/netdev/net-next/c/e82700b8662c
  - [net-next,v3,3/6] ravb: Create helper to allocate skb and align it
    https://git.kernel.org/netdev/net-next/c/cfbad64706c1
  - [net-next,v3,4/6] ravb: Use the max frame size from hardware info for RZ/G2L
    https://git.kernel.org/netdev/net-next/c/496863388136
  - [net-next,v3,5/6] ravb: Move maximum Rx descriptor data usage to info struct
    https://git.kernel.org/netdev/net-next/c/555419b2259b
  - [net-next,v3,6/6] ravb: Unify Rx ring maintenance code paths
    https://git.kernel.org/netdev/net-next/c/644d037b2c44

You are awesome, thank you!