current->need_reshed, can it be a global flag ?

From: Parity Error (bootup@mail.ru)
Date: Thu Mar 22 2001 - 07:50:09 EST

Next message: Richard B. Johnson: "RE: hostid derived from..."
Previous message: Ulrich Windl: "2.2.18: e100.c (SuSE 7.1): udelay() used in a wrong way?"
Next in thread: george anzinger: "Re: current->need_reshed, can it be a global flag ?"
Reply: george anzinger: "Re: current->need_reshed, can it be a global flag ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

instead of need_reshed being a per-task flag, could it be
as a global flag ?, since every time current->need_reshed
is checked, schedule() is just called to pick another
process.

--- Получите и Вы свой бесплатный электронный адрес на http://Mail.ru

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Next message: Richard B. Johnson: "RE: hostid derived from..."
Previous message: Ulrich Windl: "2.2.18: e100.c (SuSE 7.1): udelay() used in a wrong way?"
Next in thread: george anzinger: "Re: current->need_reshed, can it be a global flag ?"
Reply: george anzinger: "Re: current->need_reshed, can it be a global flag ?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Mar 23 2001 - 21:00:17 EST