DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wathsala Wathawana Vithanage <wathsala.vithanage@arm.com>
To: "dev@dpdk.org" <dev@dpdk.org>,
	Nathan Southern <nsouthern@linuxfoundation.org>,
	"thomas@monjalon.net" <thomas@monjalon.net>,
	 Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
Cc: nd <nd@arm.com>, nd <nd@arm.com>
Subject: RE: DPDK - PCIe Steering Tags Meeting on 10/23/24
Date: Mon, 21 Oct 2024 02:05:06 +0000	[thread overview]
Message-ID: <PAWPR08MB8909E8E4690A37846A6F74C49F432@PAWPR08MB8909.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <PAWPR08MB890910472DA9BCF9E4208E3B9F472@PAWPR08MB8909.eurprd08.prod.outlook.com>

Here is the updated RFC https://inbox.dpdk.org/dev/20241021015246.304431-1-wathsala.vithanage@arm.com/#t

Thanks

--wathsal

>
> Subject: DPDK - PCIe Steering Tags Meeting on 10/23/24
> 
> Hi all,
> 
> This is an invitation to discuss adding PCIe steering tags support to DPDK.
> We have had brief conversations over the idea at the DPDK summit.
> Steering tags allows stashing of descriptors and packet data closer to the
> CPUs, possibly allowing for lower latency and higher throughput.
> This feature requires contributions from CPU vendors and NIC vendors.
> The goal of the meeting is to present the next version of the API and seek
> support for implementation from other participants in the community.
> 
> I will be sending out the RFC some time this week, so there will be a plenty of
> time before the meeting to go over it.
> 
> Agenda:
> - Brief introduction to the feature
> - Introduce the APIs from RFC v2 (this will be submitted to the community
> before the call)
> - Dependencies on kernel support - API for reading steering tags
> - Addressing ABI in advance as patches will not be ready by 24.11
> 
> Please join the call if you are interested in the topic.
> LXF meeting registration ink: https://zoom-
> lfx.platform.linuxfoundation.org/meeting/94917063595?password=77f3662
> 5-ad41-4b9c-b067-d33e68c3a29e&invite=true
> 
> Thanks.
> 
> --wathsala


      reply	other threads:[~2024-10-21  2:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-17 19:56 Wathsala Wathawana Vithanage
2024-10-21  2:05 ` Wathsala Wathawana Vithanage [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=PAWPR08MB8909E8E4690A37846A6F74C49F432@PAWPR08MB8909.eurprd08.prod.outlook.com \
    --to=wathsala.vithanage@arm.com \
    --cc=Honnappa.Nagarahalli@arm.com \
    --cc=dev@dpdk.org \
    --cc=nd@arm.com \
    --cc=nsouthern@linuxfoundation.org \
    --cc=thomas@monjalon.net \
    /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).