DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: prateekag <prateekag@cse.iitb.ac.in>
Cc: dev@dpdk.org, honnappa.nagarahalli@arm.com
Subject: Re: [dpdk-dev] [dpdk-web] DPDK Programmer's Guide :ERRATA
Date: Sun, 26 Jan 2020 22:36:11 +0100
Message-ID: <3225697.zog1K27m0d@xps> (raw)
In-Reply-To: <c363f2be090a1516ab545653c3be52b5@cse.iitb.ac.in>

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




       reply	other threads:[~2020-01-26 21:36 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 [this message]
2020-01-27 15:33   ` Honnappa Nagarahalli

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=3225697.zog1K27m0d@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=prateekag@cse.iitb.ac.in \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git