Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

map-type: Fix preposition for BPF_F_ZERO_SEED #98

Merged
merged 1 commit into from
Dec 8, 2024
+4 −4
Merged

map-type: Fix preposition for BPF_F_ZERO_SEED #98

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/linux/map-type/BPF_MAP_TYPE_BLOOM_FILTER.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Setting this flag will initialize the hash table with a seed of 0.

The hashing algorithm used by the hash table is seeded with a random number by default. This seeding is meant as a mitigation against Denial of Service attacks which could exploit the predictability of hashing implementations.

This random seed makes hash map operations inherently random in access time. This flag was introduced to make performance evaluation more consistent.
This random seed makes hash map operations inherently random at access time. This flag was introduced to make performance evaluation more consistent.

!!! warning
It is not recommended to use this flag in production due to the vulnerability to Denial of Service attacks.
Expand Down
2 changes: 1 addition & 1 deletion docs/linux/map-type/BPF_MAP_TYPE_HASH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -86,7 +86,7 @@ Setting this flag will initialize the hash table with a seed of 0.

The hashing algorithm used by the hash table is seeded with a random number by default. This seeding is meant as a mitigation against Denial of Service attacks which could exploit the predictability of hashing implementations.

This random seed makes hash map operations inherently random in access time. This flag was introduced to make performance evaluation more consistent.
This random seed makes hash map operations inherently random at access time. This flag was introduced to make performance evaluation more consistent.

!!! warning
It is not recommended to use this flag in production due to the vulnerability to Denial of Service attacks.
Expand Down
2 changes: 1 addition & 1 deletion docs/linux/map-type/BPF_MAP_TYPE_LRU_HASH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -94,7 +94,7 @@ Setting this flag will initialize the hash table with a seed of 0.

The hashing algorithm used by the hash table is seeded with a random number by default. This seeding is meant as a mitigation against Denial of Service attacks which could exploit the predictability of hashing implementations.

This random seed makes hash map operations inherently random in access time. This flag was introduced to make performance evaluation more consistent.
This random seed makes hash map operations inherently random at access time. This flag was introduced to make performance evaluation more consistent.

!!! warning
It is not recommended to use this flag in production due to the vulnerability to Denial of Service attacks.
Expand Down
2 changes: 1 addition & 1 deletion docs/linux/map-type/BPF_MAP_TYPE_PERCPU_HASH.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@ Setting this flag will initialize the hash table with a seed of 0.

The hashing algorithm used by the hash table is seeded with a random number by default. This seeding is meant as a mitigation against Denial of Service attacks which could exploit the predictability of hashing implementations.

This random seed makes hash map operations inherently random in access time. This flag was introduced to make performance evaluation more consistent.
This random seed makes hash map operations inherently random at access time. This flag was introduced to make performance evaluation more consistent.

!!! warning
It is not recommended to use this flag in production due to the vulnerability to Denial of Service attacks.
Expand Down
Loading