Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix rst typos in benchmarking.html #2868

Merged
merged 4 commits into from
Nov 19, 2024

Conversation

gonidelis
Copy link
Member

@gonidelis gonidelis commented Nov 18, 2024

fixes and extensions on top of #2831

@gonidelis gonidelis requested review from a team as code owners November 18, 2024 22:05
@gonidelis gonidelis requested review from gevtushenko, miscco and bernhardmgruber and removed request for gevtushenko November 18, 2024 22:05
@gonidelis gonidelis force-pushed the cub_benchmarking_docs_fix branch from aba9ac4 to 10f5d9a Compare November 18, 2024 23:37
gonidelis and others added 4 commits November 18, 2024 16:20
With our devcontainers and presets dev environment it's highly likely that `cccl/` is not just a step above.
@gonidelis gonidelis force-pushed the cub_benchmarking_docs_fix branch from 10f5d9a to 0163318 Compare November 19, 2024 00:20
@@ -181,7 +187,7 @@ We can then run the full benchmark suite from the build directory with:

.. code-block:: bash

../benchmarks/scripts/run.py
<root_dir_to_cccl>/cccl/benchmarks/scripts/run.py
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remark: I wrote the documentation from the perspective of the cmake build directory. But I am not against the change, if this helps you (and users)!

@gonidelis gonidelis merged commit 052db85 into NVIDIA:main Nov 19, 2024
24 checks passed
trxcllnt pushed a commit to trxcllnt/cccl that referenced this pull request Nov 23, 2024
* Fix rst typos in benchmarking.html

* typo

* run.py script proper directory

With our devcontainers and presets dev environment it's highly likely that `cccl/` is not just a step above.

* Add `CUDA_VISIBLE_DEVICES` warning explanation so it can be avoided
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants