lkml.org 
[lkml]   [2004]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: get_current is __pure__, maybe __const__ even
    On Wed, Sep 15, 2004 at 07:15:18PM -0400, Jakub Jelinek wrote:
    >>> current will certainly change in schedule (),

    On Wed, Sep 15, 2004 at 10:10:20PM -0400, Albert Cahalan wrote:
    > Not really!

    Yes it does. The interior of schedule() is C and must be compiled also.


    At some point in the past, I wrote:
    >> Why would barrier() not suffice?

    On Wed, Sep 15, 2004 at 10:10:20PM -0400, Albert Cahalan wrote:
    > I don't think even barrier() is needed.
    > Suppose gcc were to cache the value of
    > current over a schedule. Who cares? It'll
    > be the same after schedule() as it was
    > before.

    Not over a call to schedule(). In the midst of schedule().


    -- wli
    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 14:06    [W:0.021 / U:89.516 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site