Page 1 of 2 12 LastLast
Results 1 to 10 of 17

Thread: Linux 3.17 Lands Memfd, A KDBUS Prerequisite

  1. #1
    Join Date
    Jan 2007
    Posts
    15,138

    Default Linux 3.17 Lands Memfd, A KDBUS Prerequisite

    Phoronix: Linux 3.17 Lands Memfd, A KDBUS Prerequisite

    There's many new features to Linux 3.17 that were covered over the past two weeks on Phoronix. One of the merged Linux 3.17 features that went under our radar at the time was the new memfd syscall was merged, which is a requirement of the forthcoming KDBUS, the kernel-based D-Bus implementation sought after by the systemd crew...

    http://www.phoronix.com/vr.php?view=MTc2NzQ

  2. #2
    Join Date
    May 2012
    Posts
    550

    Default

    so it's like shm_open but with using a fd instead of a name ?
    i thought it would allow changing permissions on the fly; guess i have to read better next time

  3. #3
    Join Date
    Feb 2014
    Posts
    45

    Default

    Oh look, cancer spreading...
    Yet another infection to remove before compiling...

  4. #4
    Join Date
    May 2010
    Posts
    173

    Default

    Could wayland_shm use memfds?

  5. #5
    Join Date
    Dec 2013
    Posts
    100

    Default

    Quote Originally Posted by atari314 View Post
    Oh look, cancer spreading...
    Yet another infection to remove before compiling...
    if you can do better show some code....

  6. #6
    Join Date
    Mar 2012
    Posts
    14

    Default

    How about you guys educate yourself before complaining? memfd has nothing to do with kdbus except that kdbus happens to use it. For details, see:

    http://dvdhrm.wordpress.com/2014/06/10/memfd_create2/

    You read it? Ok, now continue calling work of other people "infectious cancer" without having a clue what it is all about...

  7. #7
    Join Date
    Oct 2012
    Location
    Sweden
    Posts
    342

    Default

    Quote Originally Posted by dvdhrm View Post
    How about you guys educate yourself before complaining? memfd has nothing to do with kdbus except that kdbus happens to use it. For details, see:

    http://dvdhrm.wordpress.com/2014/06/10/memfd_create2/

    You read it? Ok, now continue calling work of other people "infectious cancer" without having a clue what it is all about...
    Thank you. I was getting annoyed with all this stupidity.

  8. #8
    Join Date
    Jul 2012
    Posts
    147

    Default

    Quote Originally Posted by atari314 View Post
    Oh look, cancer spreading...
    Yet another infection to remove before compiling...
    Why ? It is meant to enable dbus replacement that will be far leaner. What's so wrong with that ?

  9. #9
    Join Date
    Aug 2012
    Location
    Pennsylvania, United States
    Posts
    1,911

    Default

    Quote Originally Posted by Brane215 View Post
    Why ? It is meant to enable dbus replacement that will be far leaner. What's so wrong with that ?
    There's some people on these boards that do their best to rip out anything dbus related if at all possible.. theyve said so before in other Dbus related threads.

  10. #10
    Join Date
    Sep 2011
    Posts
    285

    Default

    Quote Originally Posted by Ericg View Post
    There's some people on these boards that do their best to rip out anything dbus related if at all possible.. theyve said so before in other Dbus related threads.
    no arguing with irrationality..

    someone better not tell 'em that dbus uses sockets, lest they try to build a kernel without socket support :-P

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •