Soft Patch Panel
 help / color / Atom feed
* [spp] [Bug 443] spp primary takes up the complete hugepages
@ 2020-04-06  6:25 bugzilla
  2020-04-07  8:29 ` bugzilla
                   ` (13 more replies)
  0 siblings, 14 replies; 15+ messages in thread
From: bugzilla @ 2020-04-06  6:25 UTC (permalink / raw)
  To: spp

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

            Bug ID: 443
           Summary: spp primary takes up the complete hugepages
           Product: SPP
           Version: unspecified
          Hardware: All
               URL: http://http://doc.dpdk.org/spp/setup/howto_use.html
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: main
          Assignee: yasufum.o@gmail.com
          Reporter: vipin.varghese@intel.com
                CC: spp@dpdk.org
  Target Milestone: ---

absence for 'socket-limit' options causes memory bloating for SPP. 

correction: request to add to URL option '--socket-limit' as the recommended
DPDK version is `git clone`

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
@ 2020-04-07  8:29 ` bugzilla
  2020-04-07 10:33 ` bugzilla
                   ` (12 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-07  8:29 UTC (permalink / raw)
  To: spp

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

Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |yamashita.hideyuki@ntt-tx.c
                   |                            |o.jp

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

Thanks for you reporting.
I would like to ask some questions as following.

Q1.Which SPP version you used?
Q2.Which DPDK version you used?
Q3.Can you share terminal logs?
I would like to know what you did using console.
I would like to know what happened.
Q4.What is the real problem described by this ticket?
Primary process uses too much memories? 

Thanks
Hideyuki

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
  2020-04-07  8:29 ` bugzilla
@ 2020-04-07 10:33 ` bugzilla
  2020-04-08  8:23 ` bugzilla
                   ` (11 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-07 10:33 UTC (permalink / raw)
  To: spp

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

--- Comment #2 from Vipin Varghese (vipin.varghese@intel.com) ---
Hello Hideyuki,

there is no option to raise this under `documentation`.

From the documentation:-

URL: https://doc.dpdk.org/spp/setup/getting_started.html#install-dpdk-and-spp
section: 1.2.1
DPDK version: git clone http://dpdk.org/git/dpdk

from all the examples I have tested with Dpdk 18.11 onwards, not passing
`--socket-limit ` in primary takes up all huge pages

URL: https://doc.dpdk.org/spp/setup/howto_use.html
section: 2.2
Primary command: `sudo ./src/primary/x86_64-native-linuxapp-gcc/spp_primary \
    -l 1 -n 4 \
    --socket-mem 512,512 \
    --huge-dir=/dev/hugepages \
    --proc-type=primary \
    -- \
    -p 0x03 \
    -n 10 \
    -s 192.168.1.100:5555`

Once you pass option '--socket-limit with --socket-mem' you can limit the
usage. Please update the documentation for reflecting the new memory
requirements.

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages 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
                   ` (10 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-08  8:23 UTC (permalink / raw)
  To: spp

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

--- Comment #3 from Hideyuki Yamashita (yamashita.hideyuki@ntt-tx.co.jp) ---
Thanks for your info. I will confirm what you are saying first.

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (2 preceding siblings ...)
  2020-04-08  8:23 ` bugzilla
@ 2020-04-09  8:41 ` bugzilla
  2020-04-09 10:20 ` bugzilla
                   ` (9 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-09  8:41 UTC (permalink / raw)
  To: spp

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.

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (3 preceding siblings ...)
  2020-04-09  8:41 ` bugzilla
@ 2020-04-09 10:20 ` bugzilla
  2020-04-17  8:25 ` bugzilla
                   ` (8 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-09 10:20 UTC (permalink / raw)
  To: spp

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

--- Comment #5 from Vipin Varghese (vipin.varghese@intel.com) ---
Hi Hideyuki,

But my problem is I can not imagine how those parameters are used in one piece.
Answer> are you able to run any dpdk example and observe the issue at all? If
yes, please run SPP and check the same.

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (4 preceding siblings ...)
  2020-04-09 10:20 ` bugzilla
@ 2020-04-17  8:25 ` bugzilla
  2020-04-19  6:50 ` bugzilla
                   ` (7 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-17  8:25 UTC (permalink / raw)
  To: spp

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

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

Thanks for your response.
Unfortunately I could not observe the issue using DPDK19.11+SPP19.11.

[Hugepage usage]
Before primary process invoke 
$ cat /proc/meminfo | grep -i HugePages
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
HugePages_Total:      16
HugePages_Free:       16
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

During primary process invoke
$ cat /proc/meminfo | grep -i HugePages
AnonHugePages:         0 kB
ShmemHugePages:        0 kB
HugePages_Total:      16
HugePages_Free:       14
HugePages_Rsvd:        0
HugePages_Surp:        0
Hugepagesize:    1048576 kB

It looks that only 2 pages are used per primary invokation.

[SPP primary startup parameters]
sudo ./src/primary/x86_64-native-linuxapp-gcc/spp_primary \
-l 1 \
-n 4 \
--socket-mem 512,512 \
--huge-dir /mnt/huge1G \
--proc-type primary \
-- \
-p 0x03 \
-n 10 \
-s 127.0.0.1:5555

[How to reserve hugepages]
/etc/default/grub
GRUB_CMDLINE_LINUX="DEBCONF_DEBUG=5 ksdevice=bootif default_hugepagesz=1G
hugepagesz=1G hugepages=16"


hugepages mount directory
 /mnt/huge_1GB

sudo mount |grep huge
nodev on /mnt/huge1G type hugetlbfs (rw,relatime,pagesize=1024M)

Thanks,
Hideyuki

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (5 preceding siblings ...)
  2020-04-17  8:25 ` bugzilla
@ 2020-04-19  6:50 ` bugzilla
  2020-04-19  6:55 ` bugzilla
                   ` (6 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-19  6:50 UTC (permalink / raw)
  To: spp

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

Vipin Varghese (vipin.varghese@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|Normal                      |High
           Severity|normal                      |critical

--- Comment #7 from Vipin Varghese (vipin.varghese@intel.com) ---
Hi Hideyuki,

I am not sure, whether it's the download or the missing information in the
documentation. 

URL: https://doc.dpdk.org/spp/setup/getting_started.html#setup
DPDK version: mainline from git
SPP version: spp-19.11.zip


Observation: Primary is resource allocator (huge page), without secondary it
consumes 1Gb (1 page from the hugepage). Starting of secondary without
```socket-limit``` it is free to consume next huge page.

Memory Usage:
# numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
15191 (gdb)                    54.12            3.23           57.35
15201 (spp_primary)          1040.76            2.12         1042.88
15208 (spp_nfv)              1039.82            2.29         1042.11
-------------------  --------------- --------------- ---------------
Total                        2134.70            7.64         2142.34

Note: I am increasing the priority.

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (6 preceding siblings ...)
  2020-04-19  6:50 ` bugzilla
@ 2020-04-19  6:55 ` bugzilla
  2020-04-19  6:56 ` bugzilla
                   ` (5 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-19  6:55 UTC (permalink / raw)
  To: spp

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

--- Comment #8 from Vipin Varghese (vipin.varghese@intel.com) ---
on stopping secondary we have
```
# numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
15191 (gdb)                    54.12            3.23           57.35
15201 (spp_primary)          1040.76            2.12         1042.88
-------------------  --------------- --------------- ---------------
Total                        1094.88            5.35         1100.23

```

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (7 preceding siblings ...)
  2020-04-19  6:55 ` bugzilla
@ 2020-04-19  6:56 ` bugzilla
  2020-04-19  6:56 ` bugzilla
                   ` (4 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-19  6:56 UTC (permalink / raw)
  To: spp

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

--- Comment #9 from Vipin Varghese (vipin.varghese@intel.com) ---
Primary: ``` x86_64-native-linuxapp-gcc/spp_primary -l 1-5 -n 4
--socket-mem=100,0 --proc-type=primary -w 0000:08:00.1 -w 0000:08:00.2 -- -p
0x3 -n 10 -s 127.0.0.1:5555 ```

Secondary:  ```./src/nfv/x86_64-native-linuxapp-gcc/spp_nfv
--proc-type=secondary -l 10-14 -- -n 10 -s 127.0.0.1:6666```

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (8 preceding siblings ...)
  2020-04-19  6:56 ` bugzilla
@ 2020-04-19  6:56 ` bugzilla
  2020-04-23  2:00 ` bugzilla
                   ` (3 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-19  6:56 UTC (permalink / raw)
  To: spp

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

Vipin Varghese (vipin.varghese@intel.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 OS|All                         |Linux
           Hardware|All                         |x86

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (9 preceding siblings ...)
  2020-04-19  6:56 ` bugzilla
@ 2020-04-23  2:00 ` bugzilla
  2020-04-23  2:23 ` bugzilla
                   ` (2 subsequent siblings)
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-23  2:00 UTC (permalink / raw)
  To: spp

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

masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |masahiro.nemoto.es@s1.ntt-t
                   |                            |x.co.jp

--- Comment #10 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) ---
Hello Vipin,

I tried to re-create the situation you mentioned in your reply.

Before the result I would like to confirm that you pointed out the follwoing
two points.
[Point1]
 Primary: ``` x86_64-native-linuxapp-gcc/spp_primary -l 1-5 -n 4
--socket-mem=100,0 --proc-type=primary -w 0000:08:00.1 -w 0000:08:00.2 -- -p
0x3 -n 10 -s 127.0.0.1:5555 ```

Even if --socket-mem option is specified when invoking primary process, it is
ignored.

[Point2]
By adding new EAL parameter named--socket-limit pamaeter, the situation
changes. 
Total amount of memroy allocation is limited by parameter which is specified
with --socket-limit parameter.

[Result1]
I confiremed Point1 can be re-created in my environment.
sudo ./spp_primary -l 1-2 -n 4 --socket-mem=100,100 --proc-type=primary
--huge-dir=/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1:5555

by invoking above parameter, 1gigabyte per socket are allocated.
As you mentioned parameter value of --socket-mem is IGNORED.

tx_h-yamashita@r740n15:~$ sudo numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
38174 (sudo)                    0.69            6.93            7.61
38175 (spp_primary)          1039.67         1027.32         2067.00
38183 (sudo)                    0.54            6.95            7.48
-------------------  --------------- --------------- ---------------
Total                        1040.89         1041.20         2082.09

[Result2]
sudo ./spp_primary -l 1-2 -n 4 --socket-mem=100,100 --socket-limit=10,10
--proc-type=primary --huge-dir=/mnt/huge1G -- -p 0x3 -n 10 -s 127.0.0.1:5555

With --socket-limit pameter, the situation did NOT change.
Expectation: 10 Mbytes per sockets are allocated.
Result: 1000Mbytes per sockets are allocated.

tx_h-yamashita@r740n15:~$ sudo numastat -p spp_

Per-node process memory usage (in MBs)
PID                           Node 0          Node 1           Total
-------------------  --------------- --------------- ---------------
38187 (sudo)                    0.68            6.95            7.63
38188 (spp_primary)          1039.61         1027.14         2066.75
38198 (sudo)                    0.54            6.75            7.30
-------------------  --------------- --------------- ---------------
Total                        1040.84         1040.84         2081.68

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (10 preceding siblings ...)
  2020-04-23  2:00 ` bugzilla
@ 2020-04-23  2:23 ` bugzilla
  2020-04-28  4:06 ` bugzilla
  2020-07-10  7:24 ` bugzilla
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-23  2:23 UTC (permalink / raw)
  To: spp

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

--- Comment #11 from Vipin Varghese (vipin.varghese@intel.com) ---
Hi Hideyuki,

thanks for your updates. Summarizing your findings

1. The issue can be reproduced.
2. The parameter ```--socket-mem=100,100 --socket-limit=10,10 ``` did not make
difference for you.

My Answers

1. you can move the status of the bug to `confirmed`.
2. The parameter usage ```--socket-mem=100,100 --socket-limit=10,10``` is not
correct.

Let me explain:

a. option ```socket-mem`` defines the minimum amount memory to be used form
huge page.
b. option ```socket-limit``` defines the max limit the memory to be used from
huge page.

Hence if you want to use memory from 
1. NUMA-0, it should be ```--socket-limit=100,1 --socket-mem=1024,1```
2. NUMA-1, it should be ```--socket-limit=1,100 --socket-mem=1,1024```
3. NUMA-0 and NUMA-1, it should be ```--socket-limit=100,100
--socket-mem=1024,1024```

This prevents primary or secondaries hijacking huge pages beyond
```socket-limit```

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (11 preceding siblings ...)
  2020-04-23  2:23 ` bugzilla
@ 2020-04-28  4:06 ` bugzilla
  2020-07-10  7:24 ` bugzilla
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-04-28  4:06 UTC (permalink / raw)
  To: spp

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

masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |CONFIRMED

--- Comment #12 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) ---
Hello Vipin,

Thanks for your advise.

1. Since we have acknowledged what you are saying,
   I change this ticket status to "confirmed".
2. I will add --socket-limit parameter in SPP documents
   where "--socket-mem" parameter is used.
   Update will be done with other document improvement
   because the description is not so much urgent.

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

* [spp] [Bug 443] spp primary takes up the complete hugepages
  2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages bugzilla
                   ` (12 preceding siblings ...)
  2020-04-28  4:06 ` bugzilla
@ 2020-07-10  7:24 ` bugzilla
  13 siblings, 0 replies; 15+ messages in thread
From: bugzilla @ 2020-07-10  7:24 UTC (permalink / raw)
  To: spp

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

--- Comment #13 from masahiro nemoto (masahiro.nemoto.es@s1.ntt-tx.co.jp) ---
Hello Vipin,

I found the related documents of memory management of DPDK as following.
https://software.intel.com/content/www/us/en/develop/articles/memory-in-dpdk-part-4-1811-and-beyond.html

Now I think I understand the meaning of '--socket-mem' and '--socket-limit'.
But at the same time, new questions pops up.
Can you answer those basic questions.

Q1.
If user specify enough memory with '--socket-mem'(e.g. 5Gbytes), then no need
to think
about '--socket-limit'.
(However this may risk the situation like following:
"Large memory pre-allocated but almost all memory not used, thus waste of
memory from
system perspective")

Q2.
'--socket-limit' specifies upper limit of memory usage regardless of
'--socket-mem' value.
Then what is the risk(e.g. performance) when user specify '--socket-limit'
without '--socket-mem'.

In general I understand that it is 'safe' to specify both parameters
rather than specifying only one of those.

But it depends on 'characteristic of DPDK application',right?
At least, SPP does NOT need additional memory in runtime
(rather primary process allocate memory only during initialization).

In addition, adding many parameters may lead to 'confusion' or 'mistype'
and needs much workload to update documents.

Your advice is highly appreciated.
What do you think?

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

^ permalink raw reply	[flat|nested] 15+ messages in thread

end of thread, back to index

Thread overview: 15+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-06  6:25 [spp] [Bug 443] spp primary takes up the complete hugepages 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
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

Soft Patch Panel

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


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


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