rte_memcpy.h(3)

πŸ’– rte_memcpy.h(3) πŸ’–

okay bestie, welcome to the Library Functions Manual, and this one's a lil header file that's lowkey carrying the whole packet-copying operation on its back. it's giving "small file, huge responsibilities." let's get into it 🫢


✨ NAME ✨

rte_memcpy.h β€” the header where DPDK keeps its vectorised memory-copying besties πŸ’…


✨ SYNOPSIS ✨

🌸 Functions 🌸

static void rte_mov16 (uint8_t *dst, const uint8_t *src)
static void rte_mov32 (uint8_t *dst, const uint8_t *src)
static void rte_mov48 (uint8_t *dst, const uint8_t *src)
static void rte_mov64 (uint8_t *dst, const uint8_t *src)
static void rte_mov128 (uint8_t *dst, const uint8_t *src)
static void rte_mov256 (uint8_t *dst, const uint8_t *src)
static void * rte_memcpy (void *dst, const void *src, size_t n)

πŸ¦‹ Detailed Description πŸ¦‹

Functions for vectorised implementation of memcpy().

Definition in file rte_memcpy.h. ✨

πŸ‘‘ Function Documentation πŸ‘‘

πŸ’« void rte_mov16 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 16 bytes from one location to another using optimised instructions.

The locations should not overlap. fr fr, do not do that.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

πŸ’« void rte_mov32 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 32 bytes from one location to another using optimised instructions.

The locations should not overlap.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

πŸ’« void rte_mov48 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 48 bytes from one location to another using optimised instructions.

The locations should not overlap.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

πŸ’« void rte_mov64 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 64 bytes from one location to another using optimised instructions.

The locations should not overlap.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

πŸ’« void rte_mov128 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 128 bytes from one location to another using optimised instructions.

The locations should not overlap.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

πŸ’« void rte_mov256 (uint8_t * dst, const uint8_t * src) [inline], [static] πŸ’«

Copy 256 bytes from one location to another using optimised instructions.

The locations should not overlap.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.

🌈 void * rte_memcpy (void * dst, const void * src, size_t n) [static] 🌈

Copy bytes from one location to another. The locations must not overlap. that's not a suggestion, bestie, that's the law 😭

Note πŸ‘€ This is implemented as a macro, so it's address should not be taken and care is needed as parameter expressions may be evaluated multiple times. For x86 platforms to enable the AVX-512 memcpy implementation, set -DRTE_MEMCPY_AVX512 macro in CFLAGS, or define the RTE_MEMCPY_AVX512 macro explicitly in the source file before including the rte_memcpy header file.

Parameters

  • dst β€” Pointer to the destination of the data.
  • src β€” Pointer to the source data.
  • n β€” Number of bytes to copy.

Returns

Pointer to the destination data. πŸŽ€


🌸 Author 🌸

Generated automatically by Doxygen for DPDK from the source code. not a human author, just the machine doing its thing, and honestly? iconic.


and that's the whole vibe check, bestie πŸ’– this page came to you from DPDK, Version 25.11.3, under the rte_memcpy.h(3) glow-up. go copy some bytes, safely, without overlapping, mwah πŸ«Άβœ¨πŸ’…

πŸ“¦ where this page comes from