Many ISPs need the kinds of quality shaping cake can do
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>
Subject: [LibreQoS] Fwd: [NetDev-People] 0x17: Talk, Nanotube: Turning XDP Code into Custom Hardware Pipelines for FPGA SmartNICs
Date: Sat, 7 Oct 2023 14:15:32 -0700	[thread overview]
Message-ID: <CAA93jw6AtSPH_LAXGGmVHMCGBVZOzw-ER4gSXZToGL7khS61vQ@mail.gmail.com> (raw)
In-Reply-To: <CAM0EoMn9AoaQWpk6bOKJJ_gg2pdWVgAgXZB5jwrfZyjooy_NEQ@mail.gmail.com>

---------- Forwarded message ---------
From: Jamal Hadi Salim via people <people@netdevconf.info>
Date: Sat, Oct 7, 2023 at 2:11 PM
Subject: [NetDev-People] 0x17: Talk, Nanotube: Turning XDP Code into
Custom Hardware Pipelines for FPGA SmartNICs
To: people <people@netdevconf.info>
Cc: Kimberley Jeffries <kimberleyjeffries@gmail.com>,
<program-committee@netdevconf.info>, Ricardo Coelho
<ricardocoelho@expertisesolutions.com.br>, Lael Santos
<lael.santos@expertisesolutions.com.br>, Diestelhorst, Stephan
<stephan.diestelhorst@amd.com>, <neilt@amd.com>, <kieranm@amd.com>,
<kimonk@amd.com>, <rips@amd.com>, <thcalver@amd.com>,
<stevenp@amd.com>, Jamal Hadi Salim <jhs@mojatatu.com>


Many modern NICs have built-in packet processing capabilities that can
effectively perform the type of use case that XDP is often used for.
Stephan Diestelhorst, Neil Turton, Kieran Mansley, Kimon Karras, Rip
Sohan , Thomas Calvert  and Steven Pope say that being able to
seamlessly offload this XDP code to the NIC – under the control of the
Linux networking subsystem and tooling – would increase server
efficiency and performance without affecting the user experience.

Stephan Diestelhorst et al will discuss Nanotube: an open-source
compiler that consumes standard XDP code and produces a tailor-made,
application-specific dataflow pipeline suitable for execution on FPGA
NIC platforms. They have demonstrated generated Katran on AMD/Xilinx
FPGA-based NICs to offload with throughput at line rate (100 Gbps) on
AMD NICs!

In this talk they will describe (i) the structure of the compiler;
(ii) performance of typical workloads; and (iii) how map accesses by
host software are supported using specially annotated packets over the
normal host data path. And last but not least they will discuss
requirements to allow better integration and support by the Linux
kernel, in particular the validator, map handling, and vendor-neutral
support requirements.

cheers,
jamal
_______________________________________________
people mailing list -- people@netdevconf.info
To unsubscribe send an email to people-leave@netdevconf.info


-- 
Oct 30: https://netdevconf.info/0x17/news/the-maestro-and-the-music-bof.html
Dave Täht CSO, LibreQos

           reply	other threads:[~2023-10-07 21:15 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAM0EoMn9AoaQWpk6bOKJJ_gg2pdWVgAgXZB5jwrfZyjooy_NEQ@mail.gmail.com>]

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

  List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw6AtSPH_LAXGGmVHMCGBVZOzw-ER4gSXZToGL7khS61vQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=libreqos@lists.bufferbloat.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