'cuda' 검색 결과

Investigate CUDA crashes in SGLang using logs and inputs saved before execution. Inspect tensor shapes, data types, and numerical anomalies, with guidance for separate process logs and additional CUDA debugging tools.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Investigating illegal memory access and device-side assertions
• Tracing NaN or Inf values through kernel calls
• Saving inputs before a CUDA crash

Set up machine learning training and inference on NVIDIA DGX Spark. Get guidance on choosing containers and packages, resolving CUDA compatibility errors, and checking that PyTorch can access the GPU before starting a workload.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Setting up a new DGX Spark for training or inference
• Diagnosing CUDA compatibility and import errors
• Choosing between containers and direct pip installation

Add a CUDA/C++ GPU operation to sgl-kernel using AOT, meaning compilation before use. Follow the implementation through PyTorch registration, Python API exposure, SGLang integration, correctness tests, and benchmarks that account for cache reuse.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding a CUDA/C++ operation to sgl-kernel
• Registering an operation with PyTorch and exposing a Python API
• Testing numerical results and invalid inputs

Develop lightweight CUDA operations for SGLang using JIT, which compiles code on first use. A tensor-scaling example explains implementation conventions, input validation, memory access helpers, and when to choose this approach.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Add a lightweight CUDA operation to SGLang
• Choose between JIT and ahead-of-time compilation
• Validate tensor inputs in a kernel launcher

Use this skill when the user is doing hands-on DOCA GPUNetIO programming — wiring a CUDA kernel on an NVIDIA GPU to a doca-eth queue via doca_gpu_eth_rxq / doca_gpu_eth_txq, standing up the per-CUDA-device doca_gpu context, designing the persistent CUDA kernel that drains the GPU-visible queue, running the dual capability check (DOCA cap-query plus cudaGetDeviceProperties), registering cudaMalloc pools via doca_buf_arr_create_*, or debugging DOCA_ERROR_* returns from the GPUNetIO API. Trigger even when the user does not explicitly mention "DOCA GPUNetIO" or "persistent kernel" — typical implicit phrasings include "CUDA kernel reading packets directly from the NIC", "GPU-initiated networking on BlueField", "DOCA_ERROR_DRIVER on doca_gpu_create", "nvidia_peermem not loaded", "kernel-per-packet is too slow", or "which GPU supports GPU-side packet I/O". Refuse and route elsewhere for general CUDA programming, DOCA Ethernet queue bring-up, DOCA DPA, or DOCA install — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Write and review Gradio demos for Hugging Face ZeroGPU. Configure GPU time limits and dependencies, and troubleshoot errors caused by separate worker processes, shared state, concurrent requests, or CUDA package installation.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Review GPU handlers in a Gradio demo
• Tune GPU duration and quota usage
• Fix PicklingError and stale state across worker processes

Find skills for tasks involving NVIDIA products or GPU computing using the live catalog. Get up to three relevant recommendations, with reasons, installation commands, and starter prompts; installation requires explicit approval.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find a skill for Jetson setup
• Discover skills for CUDA or GPU development
• Compare skills for NVIDIA video analysis workflows

Optimize scientific Python workloads for NVIDIA GPUs by choosing suitable libraries and reducing bottlenecks. Compare outputs with the CPU version and measure complete processing time, including data transfers, to determine whether the GPU implementation provides a useful improvement.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Assess whether slow Python processing would benefit from a GPU
• Move NumPy or pandas workloads to suitable GPU libraries
• Validate GPU results against CPU outputs

Investigate SGLang runs that freeze across multiple GPUs. It uses stack traces, communication logs, GPU memory dumps, and comparisons between processes to locate state differences, trace their causes, and guide fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Locate where a multi-GPU inference run freezes
• Compare logs from distributed processes
• Trace the first difference in process state

Extend and audit TVM's T.ptx instruction table for GPU code generation. It guides instruction definitions, checks generated assembly with CUDA tools, and aligns comments and supported forms with a chosen PTX specification version.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Adding PTX instructions or qualifiers to T.ptx
• Extending supported operand types
• Investigating ptxas certification failures

NVIDIA CUDA GPU 並列コンピューティングリファレンス。 CUDA C++ / CUDA Python, kernel, nvcc, Unified Memory, CUDA Graphs, Cooperative Groups, Green Contexts, Driver API, マルチ GPU。 PTX ISA 命令セット, state space, MMA 命令。 Blackwell チューニング, Streaming Multiprocessor, NVLink, Locality Domains, Compute Fabric Transport。 CUTLASS / CuTe DSL / CuTe C++ GEMM, Tensor Core, tcgen05, Task Scheduling, Operator API, nvMatmulHeuristics, nsight-compute, compute-sanitizer。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Integrate or upgrade cache-dit in SGLang diffusion, the image generation system. Follow guidance for resolving code conflicts, adding cache settings, testing feature combinations, and comparing generated images using quality measurements and logs.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Upgrading cache-dit in SGLang diffusion
• Resolving conflicts when porting upstream changes
• Adding per-request cache settings

Run language models locally with llama.cpp on CPUs, Apple Silicon, or AMD and Intel GPUs. The skill guides model setup, memory-saving GGUF format choices, interactive chat, and serving models through an OpenAI-compatible API.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Running a language model on a CPU-only computer
• Setting up local chat on an Apple Silicon Mac
• Choosing model quantization to fit available memory

Run model training, fine-tuning, inference, and batch jobs on Modal’s cloud GPUs. Estimate hardware needs and cost, generate Python launch scripts, run or deploy workloads, monitor logs, and retrieve results without managing remote servers.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Test CUDA code without a local GPU
• Run model training or LoRA fine-tuning on cloud GPUs
• Deploy a model inference API or vLLM service

Use this skill for hands-on DOCA GPI programming — wiring a GPU-Packet-Initiator context so a CUDA kernel drives RDMA queues directly from GPU memory without host CPU mediation. Covers picking GPI vs doca-gpunetio, the doca_gpi / domain / channel object model, the GPU-side handle handoff (doca_gpu_gpi_channel*), attaching GPU memory to a GPI domain, the domain and channel attribute objects, and debugging DOCA_ERROR_* from doca_gpi_* calls. Trigger even when the user does not explicitly mention "DOCA GPI" — implicit phrasings include "my CUDA kernel needs to post RDMA directly from GPU memory", "DOCA_ERROR_* from doca_gpi_gpu_channel_get", "how do I hand a GPU handle to my CUDA kernel", "how many channels can a GPI domain hold", or "GPU kernel driving RDMA without the host CPU on the path". Refuse and route elsewhere for the doca-gpunetio Send/Receive surface, the doca-rdma queue lifecycle, DPA-side initiation (doca-rdmi), or the CUDA programming model — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use this skill when the operator is authoring, building, loading, or debugging a custom doca-bench plug-in — a versioned shared library with DOCA_EXPERIMENTAL-marked C entry points that doca-bench loads to measure a workload class its built-in modes do not cover, with doca_bench_cuda as the shipped reference exemplar. Trigger even when the user does not say "doca-bench-extension" or "doca_bench_cuda" — typical implicit phrasings include "no built-in doca-bench mode fits my workload", "how do I benchmark a CUDA GPUNetIO RX/TX kernel", "doca-bench cannot find or load my custom .so", "extension exported symbols do not match what the parent expects", "soversion mismatch after a DOCA upgrade", or "my GPU kernel hangs because stop_flag was never set". Refuse and route elsewhere for questions about which built-in doca-bench mode to pick, DOCA GPUNetIO programming semantics, CUDA toolkit installation, or contributor work on in-tree extensions — those belong to other skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use for CUDA-Q setup, simulation targets, QPU access, and @cudaq.kernel authoring guidance.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when writing, reviewing, or optimizing CUDA kernels targeting sm_120a (RTX 5090 / Consumer Blackwell, GB202) in the imp inference engine. Triggers on CUDA/PTX kernel code, shared-memory layout, bank conflicts, tensor-core MMA (mxf4nvf4, tf32, 3xTF32/3xFP16), GEMV/GEMM/attention/quantization/GDN-scan kernels, decode tok/s under expected, kernel emitting HMMA instead of mxf4nvf4, occupancy, register pressure, __launch_bounds__, spills, PDL. Pair with `benchmark-cuda` for measurement and `check-degeneration` after hot-path changes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when benchmarking, profiling, or A/B-testing CUDA kernels or end-to-end perf in the imp inference engine on RTX 5090 (sm_120), including refreshing tests/perf_baseline.json or publishing numbers to docs/BENCHMARKS.md and the README. Triggers on "benchmark kernel", "profile cuda", "ncu", "nsys", "kernel timing", "kernel sum", "occupancy", "bandwidth bound", "compute bound", "roofline", "perf baseline", "is this regression real", "decode dropped", "aggregate throughput", "two-image A/B", "prefill kernel A/B". Do NOT use for writing/optimizing kernel code (sm120-cuda-expert) or output-quality checks (check-degeneration).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when debugging CUDA with cuda-gdb or Compute Sanitizer, reading GPU core dumps, using device printf, or triaging error codes 700, 701, 702, and 719. Not for performance: use cuda-profiling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

窓際族物語の動画生成工程（/local-videoのステップ7）だけをGoogle Colab（CUDA GPU）で実行する派生ワークフロー。ローカルMacにCUDA GPUが無くMiniMax H3を実行できないとき、ユーザーから「Colabで動画を作って」「H3をColabで回して」「LTXで動画を作って」と指示されたときに必ず使用する。台本・音声・キーフレーム生成・画像検証（ステップ1〜6）と最終結合（ステップ8〜9）はローカルで行い、動画生成だけを同梱ノートブック（H3=h3_colab.ipynb / LTX-2.5=ltx25_colab.ipynb）でColabに切り出す。セリフ（wav駆動リップシンク）はH3、セリフなしI2VチャプターはLTX-2.5も選べる。無料T4は配管検証用、本番生成はL4/A100（Pay As You Go / Colab Pro）。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Launch machine learning training jobs on local or remote GPUs. The skill checks available GPU memory, synchronizes code, saves logs, and verifies startup, with optional experiment tracking and support for Vast.ai and Modal.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Launch training on an available remote GPU
• Run experiments locally with CUDA or MPS
• Record training metrics with W&B

Choose a serving container for models deployed on SageMaker. Match the model type to a compatible image, retrieve its address from the AWS catalog, and check regional availability, CPU or GPU variants, and required host settings.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Choose a container for an LLM deployment
• Select images for embeddings and rerankers
• Check regional image addresses and GPU compatibility

Find and run local AI models with llama.cpp. Choose GGUF model files and quantization levels that fit available memory, launch a command line session or local server, and test an OpenAI-compatible API on your computer.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

• Find models to run on a local computer
• Choose quantization for available memory
• Launch and test a local OpenAI-compatible API