Soft Patch Panel
 help / color / mirror / Atom feed
From: bugzilla@dpdk.org
To: spp@dpdk.org
Subject: [spp] [Bug 443] spp primary takes up the complete hugepages
Date: Thu, 09 Apr 2020 08:41:59 +0000	[thread overview]
Message-ID: <bug-443-394-CHczSTU184@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-443-394@http.bugs.dpdk.org/>

https://bugs.dpdk.org/show_bug.cgi?id=443

--- Comment #4 from Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) ---
Hello Vipin,

Please let me know a bit more.

1.
http://doc.dpdk.org/guides/linux_gsg/linux_eal_parameters.html

I understand that socket-limit is newly added EAL parameter
which is used with existing socket-mem parameter.

But my problem is I can not imagine how those parematers 
are used in one piece.
If you have good example please let me know.

2.
Are you suggesting SPP issue document patch for existing tag (19.08)?
Or is it sufficient enough to update master branch?

BR and Thanks,
Hideyuki

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2020-04-09  8:42 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06  6:25 bugzilla
2020-04-07  8:29 ` bugzilla
2020-04-07 10:33 ` bugzilla
2020-04-08  8:23 ` bugzilla
2020-04-09  8:41 ` bugzilla [this message]
2020-04-09 10:20 ` bugzilla
2020-04-17  8:25 ` bugzilla
2020-04-19  6:50 ` bugzilla
2020-04-19  6:55 ` bugzilla
2020-04-19  6:56 ` bugzilla
2020-04-19  6:56 ` bugzilla
2020-04-23  2:00 ` bugzilla
2020-04-23  2:23 ` bugzilla
2020-04-28  4:06 ` bugzilla
2020-07-10  7:24 ` bugzilla
2020-07-20  1:12 ` bugzilla
2020-07-28  4:00 ` bugzilla
2020-07-29  0:47 ` bugzilla
2020-08-03  1:56 ` bugzilla
2020-08-03  4:49 ` bugzilla
2020-08-04  0:27 ` bugzilla
2020-08-04  1:47 ` bugzilla
2020-08-05  4:55 ` bugzilla
2020-08-05  5:52 ` bugzilla
2020-08-20  2:15 ` bugzilla
2020-08-25 11:53 ` bugzilla

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=bug-443-394-CHczSTU184@http.bugs.dpdk.org/ \
    --to=bugzilla@dpdk.org \
    --cc=spp@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).