Follow Slashdot stories on Twitter

 



Forgot your password?
typodupeerror
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×
Open Source Linux News Technology

The Linux Foundation Forms Open Source Effort To Advance IO Services (linuxfoundation.org) 46

The Linux Foundation is announcing FD.io ("Fido"), a Linux Foundation Project. FD.io is an open source project to provide an IO services framework for the next wave of network and storage software. Early support for FD.io comes from founding members 6WIND, Brocade, Cavium, Cisco, Comcast, Ericsson, Huawei, Inocybe Technologies, Intel Corporation, Mesophere, Metaswitch Networks (Project Calico), PLUMgrid and Red Hat.

Architected as a collection of sub-projects, FD.io provides a modular, extensible user space IO services framework that supports rapid development of high-throughput, low-latency and resource-efficient IO services. The design of FD.io is hardware, kernel, and deployment (bare metal, VM, container) agnostic.
This discussion has been archived. No new comments can be posted.

The Linux Foundation Forms Open Source Effort To Advance IO Services

Comments Filter:
  • GREAT... Just great... This will surely not cause the least bit of confusion at all with the existing FIDO Alliance. https://fidoalliance.org/ [fidoalliance.org]

  • by Anonymous Coward

    BUGS [die.net]

    POSIX requires that opening a file with the O_APPEND flag should have no affect on the location at which pwrite() writes data. However, on Linux, if a file is opened with O_APPEND, pwrite() appends data to the end of the file, regardless of the value of offset.

    Or is that too high a standard?

  • by Anonymous Coward

    FD.io ("Fido")

    That's not how that works, in any language. Just call it FDIO, or go register fi.do [www.nic.do] which is available if someone is willing to pay up.

  • FD.io ummm wouldnt that sound more like 'Video' than 'Fido'?
  • by Anonymous Coward

    Architected as a collection of sub-projects, FD.io provides a modular, extensible user space IO services framework that supports rapid development of high-throughput, low-latency and resource-efficient IO services. The design of FD.io is hardware, kernel, and deployment (bare metal, VM, container) agnostic.

    How about learning to do IO without C++ streams to hold your pee-pee? Or anything like that?

    Doing high-speed IO is no different than figuring out how to get the best performance from ANY hardware. You can't do it while ignoring the hardware. And abstracting away everything hides that.

    It's really simple: you can't run any hardware anywhere near its design limits if you ignore the design.

  • this is the result of the failure of the Open Group to provide a POSIX standard to do fast file descriptor checking. poll() and select() are absurdly inefficient and just about everyone with a kernel has invented their own faster alternative. your move Open Group!

    • POSIX has just fucked this up.

      I mean, consider the simpler goal: deprecating select(). select() is completely unusable in nontrivial applications, or in any library that might simply be in a process space that might have more than FD_SETSIZE file descriptors -- with the failure mode being memory corruption in practice, because who bothers checking FD_SETSIZE?

      The problem? POSIX hasn't even managed to incorporate ppoll()! So, if you're wanting to portably combine signal handling and FD monitoring, you're forc

Heard that the next Space Shuttle is supposed to carry several Guernsey cows? It's gonna be the herd shot 'round the world.

Working...