Startseite Erkunden Hilfe
Anmelden
miti
/
graphene
1
0
Fork 0
Dateien Issues 0 Pull-Requests 0 Wiki
Struktur: de42ebabe1
Branches Tags
graphene
/
Documentation
/
oldwiki
/
Run-Applications-with-SGX.md

Run-Applications-with-SGX.md 8.5 KB
Verlauf Originalformat

Run Applications with SGX

We prepared and tested the following applications in Graphene library OS. These applications can be directly built and run from the Graphene library OS source.

  • [[LMBench (v2.5) | Run Applications with SGX#running lmbench in graphene]]
  • [[Python | Run Applications with SGX#running python in graphene]]
  • [[R | Run Applications with SGX#running r in graphene]]
  • [[Lighttpd | Run Applications with SGX#running lighttpd in graphene]]
  • [[Apache | Run Applications with SGX#running apache in graphene]]
  • [[Busybox | Run Applications with SGX#running busybox in graphene]]
  • [[Bash | Run Applications with SGX#running bash in graphene]]
  • [[OpenJDK 1.7 | Run Applications with SGX#running openjdk in graphene]]

Running LMBench in Graphene

The LMBench source and scripts are stored in directory LibOS/shim/test/apps/lmbench inside the source tree. Many convenient commands are written in the Makefile inside the directory. The following steps will compile and run LMBench in SGX enclave.

cd LibOS/shim/test/apps/lmbench
make SGX=1      # compile source of lmbench and generate manifest and signature
make SGX_RUN=1  $ get enclave token
make test-graphene       # run the whole package in graphene library OS

The result of graphene runs can be found in lmbench-2.5/results/graphene. The file with the largest number as suffix will be the latest output. Sometimes, for debugging purpose, you may want to test each LMBench test individually. For doing that, you may run the following commands:

cd LibOS/shim/test/apps/lmbench
cd lmbench-2.5/bin/linux/
./pal_loader lat_syscall null    # run lat_syscall in Graphene

To run the tcp and udp latency tests:

./pal_loader lat_udp -s &        # starts a server
./pal_loader lat_udp 127.0.0.1   # starts a client
./pal_loader lat_udp -127.0.0.1  # kills the server

Running Python in Graphene

To run Python, first generate the manifest and the signature, and retrieve the token:

cd LibOS/shim/test/apps/python
make SGX=1
make SGX_RUN=1

You can run python.manifest.sgx as an executable to load any script. The manifest file is actually a script with a shebang that can be automatically loaded in PAL. Use the following commands:

./python.manifest.sgx scripts/helloworld.py
./python.manifest.sgx scripts/fibonacci.py

Running R in Graphene

To run R, first prepare the manifest:

cd LibOS/shim/test/apps/r
make SGX=1
make SGX_RUN=1

You can run R.manifest.sgx as an executable to load any script. The manifest file is actually a script with a shebang that can be automatically loaded in PAL. Use the following commands:

./R.manifest.sgx -f scripts/sample.r

Running Lighttpd in Graphene

Lighttpd can be used to test tcp latency and throughput of Graphene Library OS, in either single-threaded or multi-threaded environment. The scripts and source codes for Lighttpd can be found in LibOS/shim/test/apps/lighttpd. To compile the code base of Lighttpd that can be potentially used, run the following command:

cd LibOS/shim/test/apps/lighttpd
make SGX=1
make SGX_RUN=1

The building command will not only compile the source code, but build up manifests for Graphene, config file for Lighttpd, and test html files. We prepare the following test html files so far:

  • html/oscar-web: a snapshot of OSCAR website with php support
  • html/oscar-web-static: a snapshot of OSCAR website without php support
  • html/random/*.html: random file (non-html) created into different sizes

The server should be started manually, and tested by running apache bench from a remote client. To start the http server either in native runs or graphene runs, run the following commands:

make start-native-server or make start-graphene-server.

To start the server in multi-threaded environment, run the following commands:

make start-multithreaded-native-serve and make start-multithreaded-graphene-server.

To actually test, you should use ApacheBench. ApacheBench(ab) is an http client which can sit/run from any machine. When we benchmark lighttpd on Graphene, provided web server on Graphene is visible outside the host, one must be able to use ab from any of the lab machines. ab provides multiple options like the number of http requests, number of concurrent requests, silent mode, time delay between requests. The Ubuntu/Debian package is apache2-utils.

To test Lighttpd server with ApacheBench, first we need to start to Lighttpd server as above. There is a script run-apachebench.sh that takes two arguments: ip and port. It runs 10,000 requests (-n 10000) with 1, 2, 3, 4, and 5 maximum outstanding requests (-n 1...5). The results are saved into the same directory, and all previous output files are overwritten.

make start-graphene-server
./run-apachebench.sh <ip> <port>
# which internally calls:
#   ab -k -n 100000 -c [25:200] -t 10 http://ip:port/random/100.1.html

Running Apache in Graphene

Apache is a commercial-class web server that can be used to test tcp latency and throughput of Graphene Library OS. The scripts and source codes for Lighttpd can be found in LibOS/shim/test/apps/apache. To compile the code base of Apache and PHP module that can be potentially used, run the following command:

cd LibOS/shim/test/apps/apache
make SGX=1
make SGX_RUN=1

The building command will not only compile the source code, but build up manifests for Graphene, config file for Apache, and test html files (as described in the [[lighttpd section|Run Applications with SGX#Running Lighttpd in Graphene]]).

The server could be started manually by using the following commands:

make start-native-server or make start-graphene-server.

By default, the Apache web server is configured to run with 4 preforked worker processes, and has PHP support enabled.

To test Apache server with ApacheBench, first we need to start to Apache server as above. Run the same script to test with ApacheBench:

make start-graphene-server
./run-apachebench.sh <ip> <port>
# which internally calls:
#   ab -k -n 100000 -c [25:200] -t 10 http://ip:port/random/100.1.html

Running Busybox in Graphene

Busybox is a standalone shell including general-purpose system utilities. Running Busybox is a lot easier than running real shells such as Bash, because: first, Busybox can use vfork instead of fork to create new processes. second, Busybox can call itself as any of the utilities it includes, no need for calling some other binaries. The scripts and source code for Busybox is store in LibOS/shim/apps/busybox. To build the source code with proper manifest, simple run the following commands:

cd LibOS/shim/test/apps/busybox
make SGX=1
make SGX_RUN=1

To run busybox, either to run a shell or a utility, you may directly run busybox.manifest built in the directory as a script. For example:

./busybox.manifest.sgx sh (to run a shell)

or

./busybox.manifest.sgx ls -l (to list local directory)

Running Bash in Graphene

Bash is the most commonly used shell utilities in Linux. Bash can be run as a interactive standalone shell, or execute scripts or binaries immediately. Besides a few built-in commands, Bash mostly relies on other standalone utilities to execute commands given in the shell, such as ls, cat or grep. Therefore, supporting Bash will require supporting all the utility programs that can be potentially used. The scripts and source code for Bash is store in LibOS/shim/apps/bash. To build the source code with proper manifest, simple run the following commands:

cd LibOS/shim/test/apps/bash
make SGX=1
make SGX_RUN=1

To test Bash, you may use the benchmark suites we prepared: one is bash_test.sh, and the other is unixbench. Run one of the following commands to test Bash:

./bash.manifest.sgx bash_test.sh [times]

Running OpenJDK in Graphene

We have tested OpenJDK 1.6 and 1.7 in Graphene library OS. Newer versions of OpenJDK can potentially work, but there is no guarantee. To build OpenJDK 1.7 and generated the manifest, run the following commands:

cd LibOS/shim/test/apps/openjdk
make SGX=1
make SGX_RUN=1

The building will take several minutes and require network connection to download packages. After building OpenJDK, use the following script to run a Java program:

./run-java -cp classes HelloWorld

In run-java we specify the OpenJDK options to limit the resource used by the OpenJDK VM. We do not suggest running OpenJDK without these options, because the assumptions made by OpenJDK may cause Graphene library OS to crash.