Re: set_current_state(); vs current->state = bla;

From: Robert Love (rml@tech9.net)
Date: Wed Jan 01 2003 - 16:45:59 EST

Next message: Russell King: ""vmalloc", friends and GFP flags"
Previous message: Christoph Hellwig: "[PATCH] devfs creptomancy"
In reply to: Marc-Christian Petersen: "set_current_state(); vs current->state = bla;"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 2003-01-01 at 16:05, Marc-Christian Petersen wrote:

> $subject says it all. Is there _any_ reason why not to use set_current_state?

If you do not need the memory barrier... but then you can use
__set_current_state().

So, no, we should not open code this ever.

Robert Love

-
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: Russell King: ""vmalloc", friends and GFP flags"
Previous message: Christoph Hellwig: "[PATCH] devfs creptomancy"
In reply to: Marc-Christian Petersen: "set_current_state(); vs current->state = bla;"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jan 07 2003 - 22:00:15 EST