Re: [lustre-devel] [PATCH 08/16] staging: lustre: open code polling loop instead of using l_wait_event()

The lov_check_and_wait_active wait is usually (always?) going to be asynchronous from userspace and probably shouldn¹t contribute to load. So I guess that means schedule_timeout_idle. On 12/18/17, 1:18 AM, "lustre-devel on behalf of NeilBrown"

Re: [lustre-devel] [PATCH 08/16] staging: lustre: open code polling loop instead of using l_wait_event()

The lov_check_and_wait_active wait is usually (always?) going to be asynchronous from userspace and probably shouldn¹t contribute to load. So I guess that means schedule_timeout_idle. On 12/18/17, 1:18 AM, "lustre-devel on behalf of NeilBrown" wrote: >Two places that LWI_TIMEOUT_INTERVAL() is

[PATCH 08/16] staging: lustre: open code polling loop instead of using l_wait_event()

Two places that LWI_TIMEOUT_INTERVAL() is used, the outcome is a simple polling loop that polls every second for some event (with a limit). So write a simple loop to make this more apparent. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/llite/llite_lib.c | 11

[PATCH 08/16] staging: lustre: open code polling loop instead of using l_wait_event()

Two places that LWI_TIMEOUT_INTERVAL() is used, the outcome is a simple polling loop that polls every second for some event (with a limit). So write a simple loop to make this more apparent. Signed-off-by: NeilBrown --- drivers/staging/lustre/lustre/llite/llite_lib.c | 11 +--