tools/testing/selftests/net/lib/xdp_helper.c

File Facts

System

Linux kernel

Corpus path

tools/testing/selftests/net/lib/xdp_helper.c

Extension

.c

Size

2954 bytes

Lines

132

Domain

Support Tooling And Documentation

Bucket

tools

Inferred role

Support Tooling And Documentation: implementation source

Status

source implementation candidate

Why This File Exists

Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.

• Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• errno.h
• stdio.h
• stdlib.h
• string.h
• unistd.h
• sys/mman.h
• sys/socket.h
• linux/if_xdp.h
• linux/if_link.h
• net/if.h
• inttypes.h
• ksft.h

Detected Declarations

• function print_usage
• function bind

Annotated Snippet

if (!strcmp(argv[3], "-z")) {
			sxdp.sxdp_flags = XDP_ZEROCOPY;
		} else {
			print_usage(argv[0]);
			return 1;
		}
	}

	while (1) {
		if (bind(sock_fd, (struct sockaddr *)&sxdp, sizeof(sxdp)) == 0)
			break;

		if (errno == EBUSY && retry < 3) {
			retry++;
			sleep(1);
			continue;
		} else {
			perror("bind failed");
			munmap(umem_area, UMEM_SZ);
			close(sock_fd);
			return 1;
		}
	}

	ksft_ready();
	ksft_wait();

	/* parent program will write a byte to stdin when its ready for this
	 * helper to exit
	 */

	close(sock_fd);
	return 0;
}

Annotation

• Immediate include surface: `errno.h`, `stdio.h`, `stdlib.h`, `string.h`, `unistd.h`, `sys/mman.h`, `sys/socket.h`, `linux/if_xdp.h`.
• Detected declarations: `function print_usage`, `function bind`.
• Atlas domain: Support Tooling And Documentation / tools.
• Implementation status: source implementation candidate.

Implementation Notes

• This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
• Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
• Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.