d/shenango-bsd
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

README updates

Browse Source
This commit is contained in:
Amy Ousterhout 2019-02-23 23:41:02 -05:00 committed by Josh Fried
parent 23d54f9f3b
commit d1b17da7ae
2 changed files with 11 additions and 40 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -24,14 +24,7 @@ make clean && make
To enable debugging, build with `make DEBUG=1`.
3) Setup hugepages. We require at least 64 2MB hugepages. Run the script below
and follow the instructions for NUMA or non-NUMA systems, as appropriate.
```
./dpdk/usertools/dpdk-setup.sh
```
4) Install Rust and build a synthetic client-server application.
3) Install Rust and build a synthetic client-server application.
```
curl https://sh.rustup.rs -sSf | sh
@ -44,7 +37,7 @@ cargo update
cargo build --release
```
5) Run the synthetic application with a client and server. The client
4) Run the synthetic application with a client and server. The client
sends requests to the server, which performs a specified amount of
fake work (e.g., computing square roots for 10us), before responding.
@ -62,8 +55,10 @@ sudo ./iokerneld
## Supported Platforms
This code has been tested most thoroughly on Ubuntu 17.10, with kernel
4.14.0. It has been tested with Intel 82599ES 10 Gbit/s NICs and
Mellanox ConnectX-3 Pro 10 Gbit/s NICs. If you use Mellanox NICs, you
This code has been tested most thoroughly on Ubuntu 18.04, with kernel
4.15.0. It has been tested with Intel 82599ES 10 Gbits/s NICs and
Mellanox ConnectX-3 Pro 10 Gbits/s NICs. If you use Mellanox NICs, you
should install the Mellanox OFED as described in [DPDK's
documentation](https://doc.dpdk.org/guides/nics/mlx4.html).
documentation](https://doc.dpdk.org/guides/nics/mlx4.html). If you use
Intel NICs, you should insert the IGB UIO module and bind your NIC
interface to it (e.g., using the script `./dpdk/usertools/dpdk-setup.sh`).

30
apps/bench/README.md
View File

@ -1,33 +1,9 @@
# Threading Benchmarks
First build Shenango and Arachne, then build the benchmarks in this directory
with `make clean && make`. Run the benchmarks as described below, restricting
each to run on a single core.
First build Shenango and then build the benchmarks in this directory
with `make clean && make`. Run the main Shenango threading benchmarks
as follows (benchmarks will use a single runtime core).
## pthreads
```
taskset --cpu-list 2 ./tbench_linux
```
## Go
```
export GOMAXPROCS=1
cd go
go test -bench .
```
## Arachne
In arachne-all directory:
```
sudo ./CoreArbiter/bin/coreArbiterServer
```
In this directory:
```
./tbench_arachne
```
## Shenango
In shenango directory:
```
sudo ./iokerneld