[lkml]   [2012]   [May]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [tip:sched/numa] sched/numa: Introduce sys_numa_{t,m}bind()

    * David Rientjes <> wrote:

    > On Fri, 18 May 2012, tip-bot for Peter Zijlstra wrote:
    > > Commit-ID: 3a0fea961b98d1838f35dba51a639d40f4a5589f
    > > Gitweb:
    > > Author: Peter Zijlstra <>
    > > AuthorDate: Thu, 8 Mar 2012 17:56:08 +0100
    > > Committer: Ingo Molnar <>
    > > CommitDate: Fri, 18 May 2012 08:16:27 +0200
    > >
    > > sched/numa: Introduce sys_numa_{t,m}bind()
    > >
    > This depends on 931ea9d1a6e0 ("rcu: Implement per-domain
    > single-threaded call_srcu() state machine") from core/rcu.

    Indeed ...

    I'll rebase it to a (by that time probably upstream) srcu commit
    after the merge window, once we have more fixes, have
    incorporated suggestions, etc. - but it's still essentially an
    RFC topic: [*]

    Fundamentally, do people agree with the 'single home node'
    approach to begin with? We could turn it into a node mask,
    but that complicates things.

    For example if there's a hierarchy of nodes, low latency and
    high latency ones, then it might be valid to limit to a high
    level (high latency) node and not specify the lower level node -
    while the kernel would still know about the lower level nodes as

    Managing locality in a non-trivial cache hierarchy is hard :-/



    [*] I should probably move this to the tip:RFC/sched/numa
    branch, to make it clear what the status of the branch is,
    from the commit notification emails.

     \ /
      Last update: 2012-05-21 11:21    [W:0.025 / U:15.268 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site