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.

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

Allow for CPU-specific kernel to be set from zone_options_t #116

Open
k0ekk0ek opened this issue Dec 11, 2023 · 1 comment
Open

Allow for CPU-specific kernel to be set from zone_options_t #116

k0ekk0ek opened this issue Dec 11, 2023 · 1 comment
Labels
enhancement New feature or request
Milestone

Comments

@k0ekk0ek
Copy link
Contributor

At some point, NSD will use a more efficient database. The prototype checks what "kernel" to use repeatedly, for parsing zone files, that will also be the case (i.e. once per invocation of zone_parse). An application should select the "kernel" to use at startup for consistency.

@k0ekk0ek k0ekk0ek added the enhancement New feature or request label Dec 11, 2023
@k0ekk0ek k0ekk0ek added this to the Release 0.2.0 milestone Jul 19, 2024
@k0ekk0ek
Copy link
Contributor Author

k0ekk0ek commented Aug 1, 2024

Also include the option to set a preferred kernel (e.g. westmere, fallback), so we can include an option in NSD to "forcefully" set a specific kernel. Useful for situations where a hypervisor returns bad data for the CPUID instruction (not the case in #222, but would be useful to work around the bug from a user perspective). Also be sure to allow for convenient fetching of the associated kernel name so we can print in the NSD logs which kernel has been selected (see NLnetLabs/nsd#354).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant