net/packet/Kconfig

Source file repositories/reference/linux-study-clean/net/packet/Kconfig

File Facts

System: Linux kernel
Corpus path: net/packet/Kconfig
Extension: [no extension]
Size: 655 bytes
Lines: 26
Domain: Networking Core
Bucket: Sockets, Protocols, Packet Path, And Network Policy
Inferred role: Networking Core: build/configuration rule
Status: atlas-only

Why This File Exists

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

Networking stack implementation surface: socket APIs, protocol dispatch, packet flow, routing, filtering, and network namespaces.

Dependency Surface

No C-style include directives detected by the generator.

Detected Declarations

No top-level syscall, struct, function, initcall, or export declaration detected by the generator.

Annotated Snippet

# SPDX-License-Identifier: GPL-2.0-only
#
# Packet configuration
#

config PACKET
	tristate "Packet socket"
	help
	  The Packet protocol is used by applications which communicate
	  directly with network devices without an intermediate network
	  protocol implemented in the kernel, e.g. tcpdump.  If you want them
	  to work, choose Y.

	  To compile this driver as a module, choose M here: the module will
	  be called af_packet.

	  If unsure, say Y.

config PACKET_DIAG
	tristate "Packet: sockets monitoring interface"
	depends on PACKET
	default n
	help
	  Support for PF_PACKET sockets monitoring interface used by the ss tool.
	  If unsure, say Y.

Annotation

Atlas domain: Networking Core / Sockets, Protocols, Packet Path, And Network Policy.
Implementation status: atlas-only.

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.