Skip to content

Commit ea66271

Browse files
authored
Update README.md
1 parent 3b8cee4 commit ea66271

File tree

1 file changed

+0
-43
lines changed
  • Libraries/oneMKL/guided_cuBLAS_examples_SYCL_Migration

1 file changed

+0
-43
lines changed

Libraries/oneMKL/guided_cuBLAS_examples_SYCL_Migration/README.md

Lines changed: 0 additions & 43 deletions
Original file line numberDiff line numberDiff line change
@@ -120,49 +120,6 @@ Run the programs on a CPU or GPU. Each sample uses a default device, which in mo
120120
make run_amax
121121
```
122122

123-
### Build and Run the `cuBLAS Migration` Sample in Intel® DevCloud (Optional)
124-
125-
When running a sample in the Intel® DevCloud, you must specify the compute node (CPU, GPU, FPGA) and whether to run in batch or interactive mode. For more information, see the Intel® oneAPI Base Toolkit [Get Started Guide](https://devcloud.intel.com/oneapi/get_started/).
126-
127-
#### Build and Run Samples in Batch Mode (Optional)
128-
129-
You can submit build and run jobs through a Portable Bash Script (PBS). A job is a script that submitted to PBS through the `qsub` utility. By default, the `qsub` utility does not inherit the current environment variables or your current working directory, so you might need to submit jobs to configure the environment variables. To indicate the correct working directory, you can use either absolute paths or pass the `-d \<dir\>` option to `qsub`.
130-
131-
1. Open a terminal on a Linux* system.
132-
2. Log in to Intel® DevCloud.
133-
```
134-
ssh devcloud
135-
```
136-
3. Download the samples.
137-
```
138-
git clone https://github.com/oneapi-src/oneAPI-samples.git
139-
```
140-
4. Change to the sample directory.
141-
5. Configure the sample for a GPU node and choose the backend as OpenCL.
142-
```
143-
qsub -I -l nodes=1:gpu:ppn=2 -d .
144-
export SYCL_DEVICE_FILTER=opencl:gpu
145-
```
146-
- `-I` (upper case I) requests an interactive session.
147-
- `-l nodes=1:gpu:ppn=2` (lower case L) assigns one full GPU node.
148-
- `-d .` makes the current folder as the working directory for the task.
149-
150-
|Available Nodes |Command Options
151-
|:--- |:---
152-
| GPU |`qsub -l nodes=1:gpu:ppn=2 -d .`
153-
| CPU |`qsub -l nodes=1:xeon:ppn=2 -d .`
154-
155-
6. Perform build steps as you would on Linux.
156-
7. Run the programs.
157-
8. Clean up the project files.
158-
```
159-
make clean
160-
```
161-
9. Disconnect from the Intel® DevCloud.
162-
```
163-
exit
164-
```
165-
166123
## Example Output
167124

168125
This is example output if you built the default and ran `run_amax`.

0 commit comments

Comments
 (0)