“programming”的搜索结果

Implement structured telemetry, such as counters and events, from DOCA applications to external consumers. Guides publishing API selection, schema and source setup, build and test workflows, and debugging lifecycle errors or reports that never reach the receiver.

中文简介正在准备中。当前显示英语简介。

• Publish packet counters and bandwidth gauges from a DOCA application
• Define event fields and initialize schemas and sources
• Investigate DOCA_ERROR_BAD_STATE during event reporting

Choose or explain HSB Sensor RX packetizer fields for HOLOLINK_def.svh. Do not use for full defs, validation, or runtime APB programming.

中文简介正在准备中。当前显示原文说明。

Use this skill when the user is doing hands-on NVMe-over-Fabrics storage-target work on a BlueField DPU or ConnectX NIC with DOCA STA — standing up a doca_sta DOCA Core context that accelerates the target-side NVMe-oF data path over RDMA, defining doca_sta_subsystem targets (NQN + namespaces) backed by local NVMe-PCI backend disks (doca_sta_be), checking device support via doca_sta_cap_is_supported, sizing the per-connection I/O queues, or debugging DOCA_ERROR_* from a STA call. Trigger even when the user does not say "DOCA STA" — typical implicit phrasings include "my NVMe-oF Connect never completes", "Identify Controller times out over RoCE", "16 I/O queues at depth 1024 — does this BlueField support that", "offload the nvmf target onto the DPU", or "DOCA_ERROR_IO_FAILED on an NVMe read". Refuse and route elsewhere for DOCA install, raw RDMA data movement, raw packet I/O, flow-rule programming, or initiator-side / host NVMe stack work — those belong to other skills.

中文简介正在准备中。当前显示原文说明。

Load, configure, run, observe, and stop custom congestion control algorithms on BlueField using doca_spcx_cc. The skill guides comparisons with doca-pcc, evaluation under controlled network contention, and diagnosis of loading errors or unchanged traffic behavior.

中文简介正在准备中。当前显示英语简介。

• Choosing between SPCX and doca-pcc
• Evaluating an algorithm on a non-production network
• Investigating unchanged throughput or latency

DOCA Rivermax (doca_rmax) receive streams for timing-precise media over IP (SMPTE ST 2110 video / audio, market data, scientific feeds) on a BlueField DPU or ConnectX host, once the Rivermax SDK and its license are installed; getting the SDK or license is doca-setup / doca-public-knowledge-map territory. Trigger on "ST 2110 receive isn't getting frames", "sub-microsecond jitter on my media receiver", "NOT_SUPPORTED from doca_rmax_init", "no recv events after stream start", or "license check failing on a media receiver", even without naming Rivermax. Covers doca_rmax_in_stream sessions, the SDK + license precondition check, doca_rmax_get_*_supported capability queries, pairing with doca-eth queues and doca-flow steering, and DOCA_ERROR_* from Rivermax calls. Refuse and route elsewhere for programming the underlying queue (doca-eth), steering rules (doca-flow), PTP / clock sync (doca-firefly), or best-effort packet I/O.

中文简介正在准备中。当前显示原文说明。

Build and troubleshoot custom plug-ins for workloads that doca-bench cannot measure with its built-in modes. Use the shipped CUDA example to guide shared-library construction, check loading and version compatibility, and verify a small test before larger runs.

中文简介正在准备中。当前显示英语简介。

• Checking whether a workload needs a custom extension
• Building a GPU benchmark plug-in from the shipped example
• Diagnosing a custom shared library that will not load

Use this skill when the user is doing hands-on DOCA DPA host-side work on a BlueField — creating the `doca_dpa` Core context, loading a DPACC-compiled DPA app image (`doca_dpa_app`), creating DPA threads, launching kernels via `doca_dpa_kernel_launch_update_*`, draining `doca_dpa_completion`, running `doca_dpa_cap_*` discovery, choosing between the DPA comm component (inter-DPA messaging) and the DPA verbs component (in-kernel RDMA), or debugging `DOCA_ERROR_*` from `doca_dpa_*`. Trigger even without "DOCA DPA" or "Data-Path Accelerator": "run compute on the DPA from my host", "DPA kernel hangs, no completion", "DOCA_ERROR_DRIVER on launch", "DOCA/DPACC version skew", or "does this BlueField expose a DPA". Route elsewhere for DPA-side kernel programming itself, DPACC compiler internals, host↔DPU messaging (doca-comch), host-side RDMA (doca-rdma), and GPU-initiated networking (doca-gpunetio).

中文简介正在准备中。当前显示原文说明。

Use this skill when the user is doing hands-on DOCA Management programming against BlueField / ConnectX devices — standing up a management or representor context (doca_mgmt_dev_ctx / doca_mgmt_dev_rep_ctx), querying device caps (data-direct, caps-general), toggling congestion-control global status, modifying diagnostics-data, setting ICM quotas, or issuing a raw firmware command via doca_mgmt_raw_cmd with the right scope (CONFIGURATION / DEBUG_READ_ONLY / DEBUG_WRITE / DEBUG_WRITE_FULL). Trigger even when the user does not say "DOCA Management" — typical implicit phrasings include "fleet tool that walks every BlueField and reads device state", "toggle data-direct on a VF", "set an ICM quota per representor", "send a raw firmware command from C", "DOCA_ERROR_IO_FAILED from raw_cmd", or "fwctl ioctl is failing". Refuse and route elsewhere for mlxconfig direct operation, BFB / firmware reflash, streaming telemetry, doca_caps CLI snapshots, or DOCA install itself — those belong to other skills.

中文简介正在准备中。当前显示原文说明。

Build SHA hashing applications for BlueField or ConnectX accelerators with guidance on single-request versus chunked processing, supported algorithms, buffer sizes, memory permissions, and errors returned by the DOCA SHA API.

中文简介正在准备中。当前显示英语简介。

• Offloading SHA-256 hashing to BlueField
• Choosing single-request or chunked hashing
• Checking algorithm support and buffer limits

Use this skill when the user is doing hands-on DOCA DMA programming — bringing up a doca_dma context, configuring the single doca_dma_task_memcpy task type, sizing buffers via the doca_dma_cap_task_memcpy_* queries, setting LOCAL_READ_ONLY / LOCAL_READ_WRITE permissions on source / destination doca_mmap regions (plus doca_mmap_export_* for cross-peer copies), driving the progress engine, or debugging DOCA_ERROR_* returns. Trigger even when the user does not explicitly mention "DOCA DMA" or "doca_mmap" — typical implicit phrasings include "memcpy host buffer to BlueField without using the CPU", "offload a bulk copy to the DPU", "copy returns NOT_PERMITTED on first submit", "buffer too big for one DMA task", "task submitted but no completion", or "scatter-gather copy between two memory regions". Refuse and route elsewhere for cross-network copies (DOCA RDMA), producer/consumer messaging (DOCA Comch), DOCA Core / progress-engine internals, or DOCA install — those belong to other skills.

中文简介正在准备中。当前显示原文说明。

Connect an existing socket application to a BlueField DPU without rewriting the application. This skill guides relay placement, endpoint configuration, a single-client round-trip check, and diagnosis of refused connections or traffic that stops flowing.

中文简介正在准备中。当前显示英语简介。

• Connecting an existing socket application to BlueField
• Choosing between process, sidecar, and container deployment
• Diagnosing refused connections or missing data

Build and debug the shared foundations of DOCA applications on BlueField or ConnectX hardware. Get guidance on device capabilities, memory buffers, context lifecycles, task completion processing, and separate logging controls for the SDK and application.

中文简介正在准备中。当前显示英语简介。

• Setting up the foundations of a DOCA application
• Investigating tasks that submit but never complete
• Sharing memory buffers across DOCA libraries

Helps inspect comch communication channels between a host and a BlueField DPU using the DOCA admin tool. Explains server and connection tables and checks discrepancies with application state through a read-only inventory scan.

中文简介正在准备中。当前显示英语简介。

• Listing visible comch servers and connections
• Reading server names, process IDs, and connection counts
• Comparing admin output with application connection state

Prepare changes to live BlueField or ConnectX hardware with baseline records, a separate management connection, a maintenance window, and rehearsal on matching test hardware. Define verification and rollback steps before applying firmware or configuration changes.

中文简介正在准备中。当前显示英语简介。

• Planning a BlueField mode change
• Preparing an SR-IOV change and restart
• Reviewing firmware update and rollback procedures

Helps add DOCA capabilities to an existing DPDK packet-processing application. Guides port mapping, packet-buffer conversion, compatibility checks, builds, and debugging so developers can integrate DOCA while retaining their existing packet-processing code.

中文简介正在准备中。当前显示英语简介。

• Add DOCA capabilities to an existing DPDK application
• Map a DPDK port to a DOCA device
• Convert between DPDK and DOCA packet buffers

Use this skill for hands-on DOCA Ethernet packet-queue work on a BlueField DPU or ConnectX NIC — bringing up a `doca_eth_rxq` or `doca_eth_txq` on a port / representor / SF, picking among the four `enum doca_eth_rxq_type` values (`_REGULAR` / `_CYCLIC` / `_MANAGED_MEMPOOL` / `_SHARED_MEMPOOL`), sizing burst or scatter-gather length against the `_cap_*` queries, submitting `doca_eth_txq_task_send` / `_lso_send` (carrying packet `doca_buf`s — no `doca_eth_frame` struct exists), or debugging DOCA_ERROR_* from an Ethernet call. `doca_eth_rxq` and `doca_eth_txq` are two Core contexts; one `doca_ctx_start()` does not cover both. Trigger on implicit phrasings: "my RX queue is up but no packets arrive", "send-task returns AGAIN at line rate", "which queue type for fixed-MTU ingress", "device open fails without sudo", or "is L3 checksum offload available here". Refuse and route elsewhere for installing DOCA, flow-rule / steering programming, host↔DPU control messaging, or RDMA data movement.

中文简介正在准备中。当前显示原文说明。

LP, MILP, QP — concepts, problem-text parsing, and formulation patterns (parameters, constraints, decisions, objective). Concepts only; no API.

中文简介正在准备中。当前显示原文说明。

Model and solve optimization problems with cuOpt through Python, C/C++, or the command line. Choose linear, mixed-integer, or quadratic methods based on the decisions involved, configure stopping limits, and investigate infeasible or unbounded results.

中文简介正在准备中。当前显示英语简介。

• Modeling resource allocation problems
• Representing whole-number and yes/no decisions
• Minimizing squared error or variance

Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).

中文简介正在准备中。当前显示原文说明。

Reactive streams and event-driven programming in Golang using samber/ro — ReactiveX implementation with 150+ type-safe operators, cold/hot observables, 5 subject types (Publish, Behavior, Replay, Async, Unicast), declarative pipelines via Pipe, 40+ plugins (HTTP, cron, fsnotify, JSON, logging), automatic backpressure, error propagation, and Go context integration. Apply when using or adopting samber/ro, when the codebase imports github.com/samber/ro, or when building asynchronous event-driven pipelines, real-time data processing, streams, or reactive architectures in Go. Not for finite slice transforms (→ See `samber/cc-skills-golang@golang-samber-lo` skill).

中文简介正在准备中。当前显示原文说明。

Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang. Not for nil-safety and zero-value design without this library (→ See `samber/cc-skills-golang@golang-safety` skill), nor for native error wrapping with fmt.Errorf, errors.Is and errors.As (→ See `samber/cc-skills-golang@golang-error-handling` skill).

中文简介正在准备中。当前显示原文说明。

Apply Hunt and Thomas-inspired pragmatic programming rules when improving engineering judgment, feedback loops, DRY knowledge, orthogonality, automation, or adaptability.

中文简介正在准备中。当前显示原文说明。

Expert guide for Groovy 5 development, covering concise syntax, closures, DSLs, metaprogramming, static compilation, and integration with Java 21 and Grails

中文简介正在准备中。当前显示原文说明。

Bridge THIS Claude Code or Codex session to Telegram, Discord, Feishu/Lark, QQ, or WeChat so the user can chat with Claude from their phone. Use for: setting up, starting, stopping, or diagnosing the claude-to-im bridge daemon; forwarding Claude replies to a messaging app; any phrase like "claude-to-im", "bridge", "消息推送", "消息转发", "桥接", "连上飞书", "手机上看claude", "启动后台服务", "诊断", "查看日志", "配置". Subcommands: setup, start, stop, status, logs, reconfigure, doctor. Do NOT use for: building standalone bots, webhook integrations, or coding with IM platform SDKs — those are regular programming tasks.

中文简介正在准备中。当前显示原文说明。