From: Oleksandr Nahnybida <oleksandrn@interfacemasters.com>
To: Isaac Boukris <iboukris@gmail.com>
Cc: users@dpdk.org, Olivier Matz <olivier.matz@6wind.com>,
David Marchand <david.marchand@redhat.com>
Subject: Re: Dynamic Fields Zeroing
Date: Fri, 11 Aug 2023 12:13:04 +0300 [thread overview]
Message-ID: <CAAFk=6CDZWsob9i2CpDgK--6RYpuLMh9XV7UjTU=n87+Gh9O5g@mail.gmail.com> (raw)
In-Reply-To: <CAC-fF8RbbjpvJ2W1YFQkszEzR8697dzBO2gecsYo2yQAHVjA-w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 891 bytes --]
Hi All,
Got it, thanks.
Maybe documentation needs to be updated, because, at least in 22 LTS docs,
there are no mentions of that in 11.6.1 of the programmers guide (or I
didn't read it properly)
P.S.
I also had to find the hard way)
Best regards,
Oleksandr
On Thu, Aug 10, 2023 at 10:29 AM Isaac Boukris <iboukris@gmail.com> wrote:
> Hi,
>
> On Thu, Aug 10, 2023 at 10:05 AM David Marchand
> <david.marchand@redhat.com> wrote:
> >
> > On Wed, Aug 9, 2023 at 3:24 PM Oleksandr Nahnybida
> > <oleksandrn@interfacemasters.com> wrote:
> > >
> > > Should I expect that mbuf that I get from rx_burst, won't have
> dynfield zeroed, and I should do this myself?
> >
> > I think setting/clearing a dynfield is the responsibility of the
> > component that registered it.
>
> fwiw, that is my experience as well, although I had to find it the hard
> way :)
>
[-- Attachment #2: Type: text/html, Size: 1454 bytes --]
prev parent reply other threads:[~2023-08-11 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 13:24 Oleksandr Nahnybida
2023-08-10 7:04 ` David Marchand
2023-08-10 7:29 ` Isaac Boukris
2023-08-11 9:13 ` Oleksandr Nahnybida [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='CAAFk=6CDZWsob9i2CpDgK--6RYpuLMh9XV7UjTU=n87+Gh9O5g@mail.gmail.com' \
--to=oleksandrn@interfacemasters.com \
--cc=david.marchand@redhat.com \
--cc=iboukris@gmail.com \
--cc=olivier.matz@6wind.com \
--cc=users@dpdk.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).