lkml.org 
[lkml]   [2007]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH 0/24] make atomic_read() behave consistently across all architectures
    On Thu, Aug 16, 2007 at 11:51:42AM +1000, Paul Mackerras wrote:
    >
    > Name one such case.

    See sk_stream_mem_schedule in net/core/stream.c:

    /* Under limit. */
    if (atomic_read(sk->sk_prot->memory_allocated) < sk->sk_prot->sysctl_mem[0]) {
    if (*sk->sk_prot->memory_pressure)
    *sk->sk_prot->memory_pressure = 0;
    return 1;
    }

    /* Over hard limit. */
    if (atomic_read(sk->sk_prot->memory_allocated) > sk->sk_prot->sysctl_mem[2]) {
    sk->sk_prot->enter_memory_pressure();
    goto suppress_allocation;
    }

    We don't need to reload sk->sk_prot->memory_allocated here.

    Now where is your example again?

    Cheers,
    --
    Visit Openswan at http://www.openswan.org/
    Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
    Home Page: http://gondor.apana.org.au/~herbert/
    PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
    -
    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: 2007-08-16 04:27    [W:4.398 / U:0.064 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site