DPDK patches and discussions
 help / color / mirror / Atom feed
From: 王星 <xing_wang@realsil.com.cn>
To: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: 陈立 <dali_chen@realsil.com.cn>, 王颢 <howard_wang@realsil.com.cn>,
	"Ruifeng Wang" <Ruifeng.Wang@arm.com>, nd <nd@arm.com>,
	nd <nd@arm.com>, Hau <hau@realtek.com>
Subject: 答复: about RTL8168 PMD on ARM SoC
Date: Fri, 26 Aug 2022 02:06:12 +0000	[thread overview]
Message-ID: <fc80be1b358a4b86b97d73979ed52511@realsil.com.cn> (raw)
In-Reply-To: <AM8PR08MB58103B0769A0D79708EF0E1498729@AM8PR08MB5810.eurprd08.prod.outlook.com>


[-- Attachment #1.1: Type: text/plain, Size: 2592 bytes --]

Hi Honnappa,

The attachment is our current r8168pmd code for RTL8111/8168 Giga series
(currently 8111G, 8111H are supported, we will add others later)
I will contact the SoC vendor to consult you about this issue and let you know some details about that SoC
Thanks a lot!

BRs
Xing Wang
发件人: Honnappa Nagarahalli [mailto:Honnappa.Nagarahalli@arm.com]
发送时间: 2022年8月25日 22:41
收件人: 王星 <xing_wang@realsil.com.cn>; dev@dpdk.org
抄送: 陈立 <dali_chen@realsil.com.cn>; 王颢 <howard_wang@realsil.com.cn>; Ruifeng Wang <Ruifeng.Wang@arm.com>; nd <nd@arm.com>; nd <nd@arm.com>
主题: RE: about RTL8168 PMD on ARM SoC

Hello,
               I cannot find many details of the SoC on the internet. Does it use coherent IO? Depending on that, different barriers might be needed. Other than this, I would not think it needs anything special.

If you could send an RFC to the DPDK mailing list, I am happy to review and provide any feedback.

Thanks,
Honnappa


From: 王星 <xing_wang@realsil.com.cn<mailto:xing_wang@realsil.com.cn>>
Sent: Wednesday, August 24, 2022 9:53 PM
To: dev@dpdk.org<mailto:dev@dpdk.org>
Cc: 陈立 <dali_chen@realsil.com.cn<mailto:dali_chen@realsil.com.cn>>; 王颢 <howard_wang@realsil.com.cn<mailto:howard_wang@realsil.com.cn>>
Subject: about RTL8168 PMD on ARM SoC

Hi DPDK,

I am a pmd driver developer from Realtek NIC department,
when I was porting r8168pmd already verified on x86 to an ARM64 SoC Unisoc: UIS8650
I found that after NIC Rx init (in general, Rx ring and buffers should have been prepared for NIC to DMA read),
the NIC status reg showed RDU (Rx Descriptor Unavailable), which means NIC cannot read the proper desc content,

later I sended some packets to NIC hold by testpmd rx_only mode, HW internal Rx packet counter can grow to some value, then stuck, 8168pmd Rx debug print reported it received less packets than that value, and the print showed up even some minutes later!

I doubt the phenomenon is caused by improper HW-based IO coherency support on this ARM SoC,
I have read the ARM SoC support list on DPDK website, to name it: NV Bluefield, NXP DPAA, Marvell Octeon TX …

Does DPDK (or UIO/VFIO driver or hugetlb driver) need special HW IO cache coherency support on ARM platform, say, ACE and Device side MMU etc?
Should the SoC provide specialized UIO/VFIO driver or hugetlb driver and/or specific DPDK lib to support such user mode DMA?
Will you please give suggestions, thanks a lot!

BRs

------Please consider the environment before printing this e-mail.

[-- Attachment #1.2: Type: text/html, Size: 11544 bytes --]

[-- Attachment #2: r8168pmd-22-08-26.tar.bz2 --]
[-- Type: application/octet-stream, Size: 48577 bytes --]

  reply	other threads:[~2022-08-29  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  2:53 王星
2022-08-25 14:41 ` Honnappa Nagarahalli
2022-08-26  2:06   ` 王星 [this message]
2022-08-26  2:36   ` 答复: " 王星
2022-08-26 16:44     ` Honnappa Nagarahalli
2022-08-29 15:40       ` Hau
2022-09-02  7:17         ` Thomas Monjalon

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=fc80be1b358a4b86b97d73979ed52511@realsil.com.cn \
    --to=xing_wang@realsil.com.cn \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=Ruifeng.Wang@arm.com \
    --cc=dali_chen@realsil.com.cn \
    --cc=dev@dpdk.org \
    --cc=hau@realtek.com \
    --cc=howard_wang@realsil.com.cn \
    --cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).