From: prateekag <prateekag@cse.iitb.ac.in>
To: web@dpdk.org
Subject: [dpdk-web] DPDK Programmer's Guide :ERRATA
Date: Mon, 27 Jan 2020 00:16:16 +0530 [thread overview]
Message-ID: <c363f2be090a1516ab545653c3be52b5@cse.iitb.ac.in> (raw)
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
reply other threads:[~2020-01-26 20:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c363f2be090a1516ab545653c3be52b5@cse.iitb.ac.in \
--to=prateekag@cse.iitb.ac.in \
--cc=web@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).