[lkml]   [2009]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH 1/6] staging: android: binder: Remove some funny && usage
    2009/6/17 Daniel Walker <>:
    > On Wed, 2009-06-17 at 14:26 -0700, Arve Hjønnevåg wrote:
    >> On Wed, Jun 17, 2009 at 9:31 AM, Jeremy Fitzhardinge<> wrote:
    >> > On 06/17/09 09:08, Daniel Walker wrote:
    >> ...
    >> > Also, what its usermode ABI is, how stable it is, whether its generally
    >> > useful, does it have glibc/other library support, etc.  Would you ever want
    >> > to use this in a non-Android context?
    >> You could use this in a non-android context, but the abi is not
    >> stable. There is some documentaion of the current user space api at
    >> You
    >> can also find more information at which is
    >> where the api came from.
    > Why does all this need to be done in the kernel? Couldn't any of the
    > current IPC mechanisms be re-used to accomplish this?

    Arve can probably go into more detail here, but I believe the two
    notable properties of the binder that are not present in existing IPC
    mechanisms in the kernel (that I'm aware of) are:
    - avoiding copies by having the kernel copy from the writer into a
    ring buffer in the reader's address space directly (allocating space
    if necessary)
    - managing the lifespan of proxied remoted userspace objects that can
    be shared and passed between processes (upon which the userspace
    binder library builds its remote reference counting model)

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2009-06-19 21:23    [W:0.041 / U:9.848 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site