patches for DPDK stable branches
 help / color / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Sarosh Arif <sarosh.arif@emumba.com>
Cc: stable@dpdk.org, dev@dpdk.org, "Mcnamara,
	John" <john.mcnamara@intel.com>,
	sthemmin@microsoft.com, jerinj@marvell.com, mczekaj@marvell.com,
	"Kovacevic, Marko" <marko.kovacevic@intel.com>,
	stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH] doc: fix references to /dev/huge
Date: Fri, 31 Jul 2020 01:31:49 +0200
Message-ID: <12159348.8LVKEoW7A9@thomas> (raw)
In-Reply-To: <CABoZmYM=Uj7koNvd6swNCfVTOzT+9buksPn7hynAxCC_MUJ5hA@mail.gmail.com>

06/07/2020 10:01, Sarosh Arif:
> On Mon, Jul 6, 2020 at 1:44 AM Thomas Monjalon <thomas@monjalon.net> wrote:
> 
> > 23/06/2020 07:55, Sarosh Arif:
> > > change /dev/huge to /dev/hugepages
> > >
> > > Bugzilla ID: 492
> > > Signed-off-by: Sarosh Arif <sarosh.arif@emumba.com>
> >
> > Please could you explain why /dev/hugepages must be used,
> > in the commit log for the record?
> >
> 
>  The path /dev/huge does not exist, the correct path is  /dev/hugepages, so
> for the sake of accuracy in the documentation it should be changed.

The directory can be created.
As Anatoly said, the reason is that it is the default path
on most systems.

> >
> > FYI, a similar change was done in the website by Stephen.
> >
> 
> This bug was submitted by Stephen on bugzilla, I took notice of it and
> submitted a patch to correct it. This bug is not yet corrected on the
> website.

It is fixed in the website.


Applied with more explanations.



  reply index

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23  5:55 Sarosh Arif
2020-07-05 20:44 ` Thomas Monjalon
2020-07-06  8:01   ` Sarosh Arif
2020-07-30 23:31     ` Thomas Monjalon [this message]
2020-07-28 10:17   ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly

Reply instructions:

You may reply publically 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=12159348.8LVKEoW7A9@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=mczekaj@marvell.com \
    --cc=sarosh.arif@emumba.com \
    --cc=stable@dpdk.org \
    --cc=sthemmin@microsoft.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

patches for DPDK stable branches

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/stable/0 stable/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 stable stable/ http://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


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