DPDK patches and discussions
 help / color / mirror / Atom feed
From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Mattia Milani <mattia.milani@nokia.com>
Cc: dev@dpdk.org
Subject: Re: [Help] O-RAN Fronthaul CUS-U data structure implementation
Date: Tue, 28 May 2024 10:37:55 -0400	[thread overview]
Message-ID: <CAOE1vsMHrp4UsEEFugNBtLTWHbxyAwtL5aCpmusQYwhZBW+woA@mail.gmail.com> (raw)
In-Reply-To: <4b261fe0-de0d-4c34-8876-eb8f84fd77b0@nokia.com>

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

Hi Mattia,

Have you looked into the O-RAN OSC open fronthaul phy implementation?
https://docs.o-ran-sc.org/projects/o-ran-sc-o-du-phy/en/latest/Architecture-Overview_fh.html

Cheers,
Lincoln

On Tue, May 28, 2024 at 10:31 AM Mattia Milani <mattia.milani@nokia.com>
wrote:

> Dear DPDK Dev community,
>
> I hope this is the correct mailing list for my questions, otherwise
> please excuse me and let me know where my questions should be posted.
>
> I was looking for a data structure capable to manage O-RAN Fronthaul
> CUS-U headers (attached a screenshot of the header structure form a
> packet analyzed with Wireshark)
> but I couldn't find one.
>
> I would like to be capable to identify the different port ids but also
> the number of PRBs in the section part.
>
> I wrote my own implementation for a simple use case (I don't take in
> consideration different versions and or data directions)
> but it's enough for me at the moment.
>
> What I wanted to ask is the following:
> - Does a data structure for this kind of header already exists?
> - If it doesn't exists is it planned?
> - If it's not planned could it be of some interest?
>
> If there is interest I would be happy to share what I developed up to
> now to receive comments and/or assistance on how to make it fully
> functioning.
>
> Best regards,
> Mattia
>


-- 
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>

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

  reply	other threads:[~2024-05-28 14:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-28 14:31 Mattia Milani
2024-05-28 14:37 ` Lincoln Lavoie [this message]
2024-05-29  8:04   ` Mattia Milani
2024-05-31 12:40     ` Lincoln Lavoie
2024-06-03  6:36       ` Mattia Milani
2024-06-03 11:58         ` Lincoln Lavoie
2024-06-04  4:54           ` Mattia Milani (Nokia)

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=CAOE1vsMHrp4UsEEFugNBtLTWHbxyAwtL5aCpmusQYwhZBW+woA@mail.gmail.com \
    --to=lylavoie@iol.unh.edu \
    --cc=dev@dpdk.org \
    --cc=mattia.milani@nokia.com \
    /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).