lkml.org 
[lkml]   [2007]   [Nov]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [RFC] cpuset relative memory policies - second choice
    On Thu, 1 Nov 2007, Paul Jackson wrote:

    > > > Forcing coders to specify the same detail in multiple places, when
    > > > there is no way to validate their consistency, doesn't force them
    > > > to think or do it right. It increases the error rate due to
    > >
    > > There are always wrappers for system calls. The flags will be set in
    > > these.
    >
    > We were discussing libnuma here, not glibc. The system call wrappers
    > are in glibc. System call wrappers should not be setting optional
    > flags. They should just make the system call -- do whatever magic it
    > takes to get the provided arguments into the right registers or other
    > conventionally determined places, and invoke the necessary machine
    > instruction to trap into the kernel.

    The library interface can set flags to modify behavior.
    -
    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-11-01 18:11    [W:0.025 / U:0.336 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site