DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maryam Tahhan <mtahhan@redhat.com>
To: "Koikkara Reeny, Shibin" <shibin.koikkara.reeny@intel.com>,
	"ferruh.yigit@amd.com" <ferruh.yigit@amd.com>,
	"stephen@networkplumber.org" <stephen@networkplumber.org>,
	"lihuisong@huawei.com" <lihuisong@huawei.com>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
	"liuyonglong@huawei.com" <liuyonglong@huawei.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [v2] net/af_xdp: enable a sock path alongside use_cni
Date: Tue, 5 Dec 2023 11:31:01 +0000	[thread overview]
Message-ID: <c3ba896c-52f4-42fb-96f0-9ce0916fa2dd@redhat.com> (raw)
In-Reply-To: <DM6PR11MB399509DABAB363FCE86CEA4AA286A@DM6PR11MB3995.namprd11.prod.outlook.com>

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

On 04/12/2023 17:18, Koikkara Reeny, Shibin wrote:
>>   Prerequisites
>> @@ -223,8 +224,7 @@ Howto run dpdk-testpmd with CNI plugin:
>>            securityContext:
>>             capabilities:
>>                add:
>> -               - CAP_NET_RAW
>> -               - CAP_BPF
>> +               - NET_RAW
> Need to update the 1.3. Prerequisites.


Sorry, what are you referring to?

>
>
>>            resources:
>>              requests:
>>                hugepages-2Mi: 2Gi
>> @@ -239,14 +239,20 @@ Howto run dpdk-testpmd with CNI plugin:
>>
>>     .. _pod.yaml:https://github.com/intel/afxdp-plugins-for-
>> kubernetes/blob/v0.0.2/test/e2e/pod-1c1d.yaml
>>
>> +.. note::
>> +
>> +   For Kernel versions older than 5.19 `CAP_BPF` is also required in
>> +   the container capabilities stanza.
>> +
>>   * Run DPDK with a command like the following:
>>
>>     .. code-block:: console
>>
>>        kubectl exec -i <Pod name> --container <containers name> -- \
>> -           /<Path>/dpdk-testpmd -l 0,1 --no-pci \
>> -           --vdev=net_af_xdp0,use_cni=1,iface=<interface name> \
>> -           -- --no-mlockall --in-memory
>> +           /<Path>/dpdk-testpmd -l 0-2 --no-pci --main-lcore=2 \
>> +           --vdev net_af_xdp0,iface=<interface
>> name>,use_cni=1,uds_path=/tmp/afxdp_dp/<interface name>/afxdp.sock
>> \
>> +           --vdev net_af_xdp1,iface=e<interface
>> name>,use_cni=1,uds_path=/tmp/afxdp_dp/<interface name>/afxdp.sock
> There is a typo " iface=e<interface " == "iface=<interface"


Ack


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

  parent reply	other threads:[~2023-12-05 11:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-04 10:31 Maryam Tahhan
2023-12-04 17:18 ` Koikkara Reeny, Shibin
2023-12-04 18:41   ` Maryam Tahhan
2023-12-05 10:29     ` Koikkara Reeny, Shibin
2023-12-05 11:28       ` Maryam Tahhan
2023-12-05 11:54         ` Koikkara Reeny, Shibin
2023-12-08 17:23     ` Stephen Hemminger
     [not found]       ` <CAFdtZit1v+F1UNve4wDtVJYMSPNMdFayPKHOpTyJsn_cVgMjRQ@mail.gmail.com>
2023-12-11 13:22         ` Maryam Tahhan
2023-12-05 11:31   ` Maryam Tahhan [this message]
2023-12-05 11:49     ` Koikkara Reeny, Shibin
2023-12-05 13:43 ` Loftus, Ciara
2023-12-05 14:38   ` Maryam Tahhan
2023-12-05 14:42     ` Koikkara Reeny, Shibin
2023-12-05 18:30 ` Stephen Hemminger
2023-12-06 15:00   ` Maryam Tahhan

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=c3ba896c-52f4-42fb-96f0-9ce0916fa2dd@redhat.com \
    --to=mtahhan@redhat.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@amd.com \
    --cc=lihuisong@huawei.com \
    --cc=liuyonglong@huawei.com \
    --cc=shibin.koikkara.reeny@intel.com \
    --cc=stephen@networkplumber.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).