include/crypto/internal/engine.h

File Facts

System

Linux kernel

Corpus path

include/crypto/internal/engine.h

Extension

.h

Size

1599 bytes

Lines

59

Domain

Repository Root And Misc

Bucket

include

Inferred role

Repository Root And Misc: implementation source

Status

source implementation candidate

Why This File Exists

Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.

• Top-level or miscellaneous repository surface. Use this as map coverage unless a later manual pass promotes the file into a deeper subsystem dossier.
• Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.

Dependency Surface

• crypto/algapi.h
• crypto/engine.h
• linux/kthread.h
• linux/spinlock_types.h
• linux/types.h

Detected Declarations

• struct device
• struct crypto_engine

Annotated Snippet

struct crypto_engine {
	char			name[ENGINE_NAME_LEN];
	bool			busy;
	bool			running;

	bool			retry_support;
	bool			rt;

	struct list_head	list;
	spinlock_t		queue_lock;
	struct crypto_queue	queue __guarded_by(&queue_lock);
	struct device		*dev;

	struct kthread_worker           *kworker;
	struct kthread_work             pump_requests;

	void				*priv_data;
	struct crypto_async_request	*cur_req;
};

#endif

Annotation

• Immediate include surface: `crypto/algapi.h`, `crypto/engine.h`, `linux/kthread.h`, `linux/spinlock_types.h`, `linux/types.h`.
• Detected declarations: `struct device`, `struct crypto_engine`.
• Atlas domain: Repository Root And Misc / include.
• 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.