From: Maryam Tahhan <mtahhan@redhat.com>
To: "Loftus, Ciara" <ciara.loftus@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>,
"Koikkara Reeny, Shibin" <shibin.koikkara.reeny@intel.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 14:38:17 +0000 [thread overview]
Message-ID: <20c3ea18-3615-486d-b3c2-34d8075d1e02@redhat.com> (raw)
In-Reply-To: <MW4PR11MB5872BBC93DCB83EC8F4E1D0C8E85A@MW4PR11MB5872.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 387 bytes --]
On 05/12/2023 13:43, Loftus, Ciara wrote:
>> also be provided\n",
> Thanks for the patch Maryam.
> Do we really need the use_cni devarg anymore if we must also always pair it with a uds_path string?
> I am in favour of removing it if both yourself and Shibin think that makes sense too.
>
> Ciara
Hey Ciara
I'm happy to remove the use_cni arg in favour of just the uds_path
BR
Maryam
[-- Attachment #2: Type: text/html, Size: 928 bytes --]
next prev parent reply other threads:[~2023-12-05 14:40 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
2023-12-05 11:49 ` Koikkara Reeny, Shibin
2023-12-05 13:43 ` Loftus, Ciara
2023-12-05 14:38 ` Maryam Tahhan [this message]
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=20c3ea18-3615-486d-b3c2-34d8075d1e02@redhat.com \
--to=mtahhan@redhat.com \
--cc=ciara.loftus@intel.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).