Return to Question

I'm working on a project where I want to study the impact of process priority on system behavior.

I know that tools like nice, renice, and chrt can change the priority or scheduling policy (e.g., SCHED_FIFO, SCHED_RR, etc.) from user space using system calls.

However, I’m wondering:

Is there any technical or practical advantage to adjusting process priority using a kernel module instead of via user-space tools like nice or chrt?

Have you encountered cases where a kernel module offered more control or precision in setting scheduling parameters than user-space methods?

Any insights or examples would be appreciated!

Edit More specifically:

Can setting the priority directly in the kernel (e.g., during process creation or in a module) reduce the chance of early interruptions or scheduling delays?

Is there any behavioral or performance gain from assigning SCHED_FIFO 99 at the earliest possible point, compared to launching the process with chrt -f 99 ?

I'm working in a forensics-related context where I want the memory acquisition process to be as undisturbed and deterministic as possible.

I'm working on a project where I want to study the impact of process priority on system behavior.

I know that tools like nice, renice, and chrt can change the priority or scheduling policy (e.g., SCHED_FIFO, SCHED_RR, etc.) from user space using system calls.

However, I’m wondering:

Is there any technical or practical advantage to adjusting process priority using a kernel module instead of via user-space tools like nice or chrt?

Have you encountered cases where a kernel module offered more control or precision in setting scheduling parameters than user-space methods?

Any insights or examples would be appreciated!

Edit

More specifically:

Can setting the priority directly in the kernel (e.g., during process creation or in a module) reduce the chance of early interruptions or scheduling delays?

Is there any behavioral or performance gain from assigning SCHED_FIFO 99 at the earliest possible point, compared to launching the process with chrt -f 99 ?

I'm working in a forensics-related context where I want the memory acquisition process to be as undisturbed and deterministic as possible.

I'm working on a project where I want to study the impact of process priority on system behavior.

I know that tools like nice, renice, and chrt can change the priority or scheduling policy (e.g., SCHED_FIFO, SCHED_RR, etc.) from user space using system calls.

However, I’m wondering:

Is there any technical or practical advantage to adjusting process priority using a kernel module instead of via user-space tools like nice or chrt?

Have you encountered cases where a kernel module offered more control or precision in setting scheduling parameters than user-space methods?

Any insights or examples would be appreciated!

Edit: More specifically:

Can setting the priority directly in the kernel (e.g., during process creation or in a module) reduce the chance of early interruptions or scheduling delays?

Is there any behavioral or performance gain from assigning SCHED_FIFO 99 at the earliest possible point, compared to launching the process with chrt -f 99 ?

I'm working in a forensics-related context where I want the memory acquisition process to be as undisturbed and deterministic as possible.

I'm working on a project where I want to study the impact of process priority on system behavior.

I know that tools like nice, renice, and chrt can change the priority or scheduling policy (e.g., SCHED_FIFO, SCHED_RR, etc.) from user space using system calls.

However, I’m wondering:

Is there any technical or practical advantage to adjusting process priority using a kernel module instead of via user-space tools like nice or chrt?

Have you encountered cases where a kernel module offered more control or precision in setting scheduling parameters than user-space methods?

Any insights or examples would be appreciated!

Edit More specifically:

Can setting the priority directly in the kernel (e.g., during process creation or in a module) reduce the chance of early interruptions or scheduling delays?

Is there any behavioral or performance gain from assigning SCHED_FIFO 99 at the earliest possible point, compared to launching the process with chrt -f 99 ?

I'm working in a forensics-related context where I want the memory acquisition process to be as undisturbed and deterministic as possible.