From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 44E28A00BE for ; Mon, 16 May 2022 09:38:30 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 395A842685; Mon, 16 May 2022 09:38:30 +0200 (CEST) Received: from mx-m2.obspm.fr (mx-m2.obspm.fr [145.238.186.20]) by mails.dpdk.org (Postfix) with ESMTP id 9DD1E40E64 for ; Thu, 12 May 2022 14:41:58 +0200 (CEST) Received: from [10.179.37.227] (mobility-sec02.thalesgroup.com [192.54.144.226] (may be forged)) (authenticated bits=0) by mx-m2.obspm.fr (8.15.2/8.15.2/DIO Observatoire de Paris - 15/04/10) with ESMTPSA id 24CCfv0C022447 (version=TLSv1.3 cipher=TLS_AES_128_GCM_SHA256 bits=128 verify=NOT) for ; Thu, 12 May 2022 14:41:58 +0200 From: Julien Plante To: users@dpdk.org Subject: Jumbo Frames on Memif PMD Message-ID: <81c0f2aa-a469-0e1c-a9f6-d4762dad92e8@obspm.fr> Date: Thu, 12 May 2022 14:41:57 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------7A5EBCEFB598840C35975BEE" Content-Language: en-US X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.2 (mx-m2.obspm.fr [145.238.186.20]); Thu, 12 May 2022 14:41:58 +0200 (CEST) X-Virus-Scanned: clamav-milter 0.103.5 at mx-m2 X-Virus-Status: Clean X-Mailman-Approved-At: Mon, 16 May 2022 09:38:29 +0200 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org This is a multi-part message in MIME format. --------------7A5EBCEFB598840C35975BEE Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Hi, I'm trying to use the memif PMD with Jumbo Frames, without any success yet. Please note that I'm currently using DPDK 21.11, but could consider updating. On standard packet size, I'm able to transmit packets using memif with the following commands: Terminal 1 (receiver, launch first): # ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server --file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=1518 Terminal 2 (sender, launch second): # ./dpdk-testpmd -l 0-1 --vdev=net_memif0,id=0,role=client --file-prefix=pmd2 -- --forward-mode=txonly --max-pkt-len=1518 When trying to send Jumbo Frames, I get an error on the server launch: # ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server --file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=9000 ... Frame size (9000) > device max frame size (1518) for port_id 0 ... Do you know if it is possible to increase this device max frame size for the memif PMD ? About what I tried: - Changing the bsize (Size of single packet buffer) option of the PMD to a value higher than 9000 (I tried 9000 and 2^14=16384).  I did not understand what this parameter changes, but it did not seem to help, the error stayed the same. - Reading the doc (both DPDK 's and VPP 's), searching for MTU limitations, but saw no such thing. - Start from the error message to find where the device max frame size is set. It is initialized at drivers/net/memif/rte_eth_memif.c:198,  to the value RTE_ETHER_MAX_LEN (1518), and left untouched after that. Is there any reason to limit the PMD to this value, or we could  add a setter for this value ? Thanks for any help on this issue, Julien --------------7A5EBCEFB598840C35975BEE Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit

Hi,

I'm trying to use the memif PMD with Jumbo Frames, without any success yet.
Please note that I'm currently using DPDK 21.11, but could consider updating.


On standard packet size, I'm able to transmit packets using memif with the following commands:

Terminal 1 (receiver, launch first):
# ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server --file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=1518

Terminal 2 (sender, launch second):
# ./dpdk-testpmd -l 0-1 --vdev=net_memif0,id=0,role=client --file-prefix=pmd2 -- --forward-mode=txonly --max-pkt-len=1518


When trying to send Jumbo Frames, I get an error on the server launch:

# ./dpdk-testpmd -l 2-3 --vdev=net_memif0,id=0,role=server --file-prefix=pmd1 -- --forward-mode=rxonly --max-pkt-len=9000
...
Frame size (9000) > device max frame size (1518) for port_id 0
...


Do you know if it is possible to increase this device max frame size for the memif PMD ?


About what I tried:

- Changing the bsize (Size of single packet buffer) option of the PMD to a value higher than 9000 (I tried 9000 and 2^14=16384).
 I did not understand what this parameter changes, but it did not seem to help, the error stayed the same.

- Reading the doc (both DPDK's and VPP's), searching for MTU limitations, but saw no such thing.

- Start from the error message to find where the device max frame size is set. It is initialized at drivers/net/memif/rte_eth_memif.c:198,
 to the value RTE_ETHER_MAX_LEN (1518), and left untouched after that. Is there any reason to limit the PMD to this value, or we could
 add a setter for this value ?


Thanks for any help on this issue,
Julien


--------------7A5EBCEFB598840C35975BEE--