[Doc] Update docs to clarify cache-related environment variables. #15795
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
Author
|
@intel/dpcpp-doc-reviewers ping |
AlexeySachkov
approved these changes
Oct 23, 2024
Contributor
Author
|
@intel/llvm-gatekeepers the PR is ready to be merged. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have two caches: in-memory and persistent. For some cache-related environment variables, it is not explicitly clear whether they are applicable for in-memory cache or persistent. So, this PR clarifies the description of cache-related environment variables.
Side note: I see that we never use
SYCL_CACHE_EVICTION_DISABLE,SYCL_CACHE_MAX_SIZE, andSYCL_CACHE_THRESHOLDin the code base, yet we have them in the documentation. I think, for now, we can just leave them as it is since I'm working on implementing cache eviction and I can reuse them in future.