From: Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
To: "thomas@monjalon.net" <thomas@monjalon.net>,
prateekag <prateekag@cse.iitb.ac.in>
Cc: "dev@dpdk.org" <dev@dpdk.org>, nd <nd@arm.com>,
Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>,
nd <nd@arm.com>
Subject: Re: [dpdk-dev] [dpdk-web] DPDK Programmer's Guide :ERRATA
Date: Mon, 27 Jan 2020 15:33:12 +0000 [thread overview]
Message-ID: <VE1PR08MB514963C52B2442AB3F956EDD980B0@VE1PR08MB5149.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <3225697.zog1K27m0d@xps>
Thanks Prateek for the comments. Agree with both the corrections. Would you like to submit a patch?
Thanks,
Honnappa
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Sunday, January 26, 2020 3:36 PM
> To: prateekag <prateekag@cse.iitb.ac.in>
> Cc: dev@dpdk.org; Honnappa Nagarahalli <Honnappa.Nagarahalli@arm.com>
> Subject: Re: [dpdk-web] DPDK Programmer's Guide :ERRATA
>
> Thanks for the comments.
> I did not look at this doc but I'm sure Honnappa will have answers.
>
> Note: you may want to update the doc yourself by making a patch for the
> DPDK git.
>
> Rerouting this email to dpdk-dev and adding Honnappa.
>
> 26/01/2020 19:46, prateekag:
> > Dear,
> >
> > I am currently going through the DPDK programmer's guide 20.02-rc1
> > updated on January 21, 2020, as a part of my Master's Project.
> > I found the following errors in the documentation.
> > a) In section 5.1 (What is quiescent state): In paragraph 5, The
> > line "So reader thread 1 will not have a reference to the deleted
> > entry" should be replaced with "So reader thread 3 will not have a
> > reference to the deleted entry." We are talking about reader thread 3
> > and its behavior in this paragraph and not reader thread 1."
> > b) If what I am thinking is right, this one is a much serious error.
> > In section 6.5.3 Multiple Producers enqueue Figure 6.10, the global
> > prod_head(ring-> prod_head) should point one place to the right of the
> > obj5 (i.e. shift it from its current position to one place right) As
> > in third step, core 2 CAS is successful as mention in the text.
> > If I am not mailing to the correct mailing list, kindly forward the
> > message to the correct mailing list.
> >
> > Regards
> > Prateek Agarwal
>
>
prev parent reply other threads:[~2020-01-27 15:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c363f2be090a1516ab545653c3be52b5@cse.iitb.ac.in>
2020-01-26 21:36 ` Thomas Monjalon
2020-01-27 15:33 ` Honnappa Nagarahalli [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=VE1PR08MB514963C52B2442AB3F956EDD980B0@VE1PR08MB5149.eurprd08.prod.outlook.com \
--to=honnappa.nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=prateekag@cse.iitb.ac.in \
--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).