From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Loftus, Ciara" <ciara.loftus@intel.com>,
"Tahhan, Maryam" <mtahhan@redhat.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>,
"Marchand, David" <david.marchand@redhat.com>,
"Koikkara Reeny, Shibin" <shibin.koikkara.reeny@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [v14 0/3] net/af_xdp: fix multi interface support for K8s
Date: Fri, 19 Apr 2024 12:00:25 +0100 [thread overview]
Message-ID: <e729dc1b-dec3-4805-ae28-18fbae47da52@amd.com> (raw)
In-Reply-To: <MW4PR11MB58722C71B7D5704A045649B48E002@MW4PR11MB5872.namprd11.prod.outlook.com>
On 4/8/2024 2:19 PM, Loftus, Ciara wrote:
>> The original `use_cni` implementation was limited to
>> supporting only a single netdev in a DPDK pod. This patchset
>> aims to fix this limitation transparently to the end user.
>> It will also enable compatibility with the latest AF_XDP
>> Device Plugin.
>>
>> Signed-off-by: Maryam Tahhan <mtahhan@redhat.com>
> Thanks Maryam.
>
> For the series,
> Acked-by: Ciara Loftus <ciara.loftus@intel.com>
>
Series applied to dpdk-next-net/main, thanks.
next prev parent reply other threads:[~2024-04-19 11:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 13:09 Maryam Tahhan
2024-04-08 13:09 ` [v14 1/3] docs: AF_XDP Device Plugin Maryam Tahhan
2024-04-19 10:13 ` Ferruh Yigit
2024-04-22 14:53 ` Maryam Tahhan
2024-04-22 16:14 ` Ferruh Yigit
2024-04-08 13:09 ` [v14 2/3] net/af_xdp: fix multi interface support for K8s Maryam Tahhan
2024-04-08 13:09 ` [v14 3/3] net/af_xdp: support AF_XDP DP pinned maps Maryam Tahhan
2024-04-08 13:19 ` [v14 0/3] net/af_xdp: fix multi interface support for K8s Loftus, Ciara
2024-04-19 11:00 ` Ferruh Yigit [this message]
2024-04-18 21:52 ` Ferruh Yigit
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=e729dc1b-dec3-4805-ae28-18fbae47da52@amd.com \
--to=ferruh.yigit@amd.com \
--cc=ciara.loftus@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=lihuisong@huawei.com \
--cc=liuyonglong@huawei.com \
--cc=mtahhan@redhat.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).