DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Sudharshan Krishnakumar <sudhar.ckrishna@gmail.com>,
	"dev@dpdk.org" <dev@dpdk.org>, "users@dpdk.org" <users@dpdk.org>,
	"Yang, Qiming" <qiming.yang@intel.com>
Subject: RE: regarding Intel E810
Date: Mon, 7 Mar 2022 11:54:59 +0000	[thread overview]
Message-ID: <6bb45ada77f34e4785c641f3c6f2dd95@intel.com> (raw)
In-Reply-To: <CAEm3rUk26jYScAhJ3wUU_qseG4NWVcNV9s0tO46hO3Gm=5Y6Tw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1707 bytes --]

Hi Krishnakumar:

I’m not an expert on SGX, but as I know there are many limitations to running code in the SGX enclave due to security considerations. usually, the DMA should be setup outside of the SGX, so I guess you should not run rte_eal_init within SGX.

Regards
Qi

From: Sudharshan Krishnakumar <sudhar.ckrishna@gmail.com>
Sent: Saturday, March 5, 2022 5:38 AM
To: dev@dpdk.org; users@dpdk.org; Yang, Qiming <qiming.yang@intel.com>; Zhang, Qi Z <qi.z.zhang@intel.com>
Subject: regarding Intel E810

Hi All,
I am using Intel E810 with DPDK v20.11, with ethernet ports bound to DPDK(vfio-pci).
Running DPDK software libraries within a secure-enclave(Intel SGX technology) sandbox environment,
and running into an issue during rte_eal_init invocation.
During launch of DPDK application(examples/packet_ordering), when rte_eal_init gets called,
it results in a probe of ethernet devices,which invokes ICE(Intel E810 NIC) Poll-Mode-Driver(PMD) apis.

When ICE PMD driver sends command to NIC(Network Interface Card),to get firmware version,
it times out in this api-> ice_sq_send_cmd_nolock().
Question-> Can someone point me to any Intel documentation for E810,
that describes how ICE PMD(or any software driver) can communicate with E810 NIC's firmware,
like what registers to write the command, and how to check for the response from firmware.

Question-> Also, is there any other alternate way(other than ethtool), to check if firmware received the command,
and what was the status of the last command processed by firmware.
Note: Even if there is a way to check firmware command status thro ethtool,
I cant use ethtool,since ports are bound to DPDK.

Thanks,
Sudha

[-- Attachment #2: Type: text/html, Size: 4877 bytes --]

      reply	other threads:[~2022-03-07 11:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-04 21:37 Sudharshan Krishnakumar
2022-03-07 11:54 ` Zhang, Qi Z [this message]

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=6bb45ada77f34e4785c641f3c6f2dd95@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=sudhar.ckrishna@gmail.com \
    --cc=users@dpdk.org \
    /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).