CUDA: add a flag "GGML_CUDA_JETSON_DEVICE" for optimization #13861
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.
As described in (#13856), this PR introduces a build flag (GGML_CUDA_JETSON_DEVICE) for CUDA Jetson-related optimizations and modifies the logic of cuda_device_support_buft when the flag is enabled.
The specific modification logic of “cuda_device_support_buft” is to add support for host_buffer (pinned memory) when cuda_device is jetson
According to the nvidia official website manual:https://docs.nvidia.com/cuda/cuda-for-tegra-appnote/index.html#memory-types-table