mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: Simon Horman <horms@kernel.org>,
	Vishvambar Panth S <vishvambarpanth.s@microchip.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<kuba@kernel.org>, <bryan.whitehead@microchip.com>,
	<UNGLinuxDriver@microchip.com>, <davem@davemloft.net>,
	<edumazet@google.com>, <pabeni@redhat.com>
Subject: Re: [PATCH net-next] net: microchip: lan743x : bidirectional throughput improvement
Date: Fri, 17 Nov 2023 15:51:07 -0800	[thread overview]
Message-ID: <03b2fde9-945c-4b28-9177-5e195c866c32@intel.com> (raw)
In-Reply-To: <20231117181602.GP164483@vergenet.net>



On 11/17/2023 10:16 AM, Simon Horman wrote:
> On Thu, Nov 16, 2023 at 11:13:50AM +0530, Vishvambar Panth S wrote:
>> The LAN743x/PCI11xxx DMA descriptors are always 4 dwords long, but the
>> device supports placing the descriptors in memory back to back or
>> reserving space in between them using its DMA_DESCRIPTOR_SPACE (DSPACE)
>> configurable hardware setting. Currently DSPACE is unnecessarily set to
>> match the host's L1 cache line size, resulting in space reserved in
>> between descriptors in most platforms and causing a suboptimal behavior
>> (single PCIe Mem transaction per descriptor). By changing the setting
>> to DSPACE=16 many descriptors can be packed in a single PCIe Mem
>> transaction resulting in a massive performance improvement in
>> bidirectional tests without any negative effects.
>> Tested and verified improvements on x64 PC and several ARM platforms
>> (typical data below)
>>
>> Test setup 1: x64 PC with LAN7430 ---> x64 PC
>>
>> iperf3 UDP bidirectional with DSPACE set to L1 CACHE Size:
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID][Role] Interval           Transfer     Bitrate
>> [  5][TX-C]   0.00-10.00  sec   170 MBytes   143 Mbits/sec  sender
>> [  5][TX-C]   0.00-10.04  sec   169 MBytes   141 Mbits/sec  receiver
>> [  7][RX-C]   0.00-10.00  sec  1.02 GBytes   876 Mbits/sec  sender
>> [  7][RX-C]   0.00-10.04  sec  1.02 GBytes   870 Mbits/sec  receiver
>>
>> iperf3 UDP bidirectional with DSPACE set to 16 Bytes
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID][Role] Interval           Transfer     Bitrate
>> [  5][TX-C]   0.00-10.00  sec  1.11 GBytes   956 Mbits/sec  sender
>> [  5][TX-C]   0.00-10.04  sec  1.11 GBytes   951 Mbits/sec  receiver
>> [  7][RX-C]   0.00-10.00  sec  1.10 GBytes   948 Mbits/sec  sender
>> [  7][RX-C]   0.00-10.04  sec  1.10 GBytes   942 Mbits/sec  receiver
>>
>> Test setup 2 : RK3399 with LAN7430 ---> x64 PC
>>
>> RK3399 Spec:
>> The SOM-RK3399 is ARM module designed and developed by FriendlyElec.
>> Cores: 64-bit Dual Core Cortex-A72 + Quad Core Cortex-A53
>> Frequency: Cortex-A72(up to 2.0GHz), Cortex-A53(up to 1.5GHz)
>> PCIe: PCIe x4, compatible with PCIe 2.1, Dual operation mode
>>
>> iperf3 UDP bidirectional with DSPACE set to L1 CACHE Size:
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID][Role] Interval           Transfer     Bitrate
>> [  5][TX-C]   0.00-10.00  sec   534 MBytes   448 Mbits/sec  sender
>> [  5][TX-C]   0.00-10.05  sec   534 MBytes   446 Mbits/sec  receiver
>> [  7][RX-C]   0.00-10.00  sec  1.12 GBytes   961 Mbits/sec  sender
>> [  7][RX-C]   0.00-10.05  sec  1.11 GBytes   946 Mbits/sec  receiver
>>
>> iperf3 UDP bidirectional with DSPACE set to 16 Bytes
>> - - - - - - - - - - - - - - - - - - - - - - - - -
>> [ ID][Role] Interval           Transfer     Bitrate
>> [  5][TX-C]   0.00-10.00  sec   966 MBytes   810 Mbits/sec   sender
>> [  5][TX-C]   0.00-10.04  sec   965 MBytes   806 Mbits/sec   receiver
>> [  7][RX-C]   0.00-10.00  sec  1.11 GBytes   956 Mbits/sec   sender
>> [  7][RX-C]   0.00-10.04  sec  1.07 GBytes   919 Mbits/sec   receiver
>>
>> Signed-off-by: Vishvambar Panth S <vishvambarpanth.s@microchip.com>
> 
> Thanks,
> 
> I think you should have included Jacob's Reviewed-by tag from
> the previous posting of this patch [1].
> 
> And echoing his comments there, a very nice performance boost :)
> 
> Reviewed-by: Simon Horman <horms@kernel.org>
> 
> [1] https://lore.kernel.org/netdev/e5ffec56-5512-1acc-b85c-ac0771634c22@intel.com/

For the record, this version also looks good to me!

Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>

  reply	other threads:[~2023-11-17 23:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16  5:43 Vishvambar Panth S
2023-11-17 18:16 ` Simon Horman
2023-11-17 23:51   ` Jacob Keller [this message]
2023-11-17 18:22 ` Florian Fainelli
2023-11-21  2:00 ` patchwork-bot+netdevbpf

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=03b2fde9-945c-4b28-9177-5e195c866c32@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=bryan.whitehead@microchip.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=vishvambarpanth.s@microchip.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

all inboxes | Powered by JetHome®