include/crypto/gf128mul.h
Source file repositories/reference/linux-study-clean/include/crypto/gf128mul.h
File Facts
- System
- Linux kernel
- Corpus path
include/crypto/gf128mul.h- Extension
.h- Size
- 9210 bytes
- Lines
- 238
- 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
asm/byteorder.hcrypto/b128ops.hlinux/slab.h
Detected Declarations
struct gf128mul_64kfunction gf128mul_mask_from_bitfunction gf128mul_x_llefunction gf128mul_x_bbefunction gf128mul_x_ble
Annotated Snippet
struct gf128mul_64k {
struct {
be128 t[256];
} *t[16];
};
/* First initialize with the constant factor with which you
* want to multiply and then call gf128mul_64k_bbe with the other
* factor in the first argument, and the table in the second.
* Afterwards, the result is stored in *a.
*/
struct gf128mul_64k *gf128mul_init_64k_bbe(const be128 *g);
void gf128mul_free_64k(struct gf128mul_64k *t);
void gf128mul_64k_bbe(be128 *a, const struct gf128mul_64k *t);
#endif /* _CRYPTO_GF128MUL_H */
Annotation
- Immediate include surface: `asm/byteorder.h`, `crypto/b128ops.h`, `linux/slab.h`.
- Detected declarations: `struct gf128mul_64k`, `function gf128mul_mask_from_bit`, `function gf128mul_x_lle`, `function gf128mul_x_bbe`, `function gf128mul_x_ble`.
- 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.