File:  [NetBSD Developer Wiki] / wikisrc / projects / project / binary_compat_puffs_backend.mdwn
Revision 1.2: download - view: text, annotated - select for diffs
Sun Nov 6 14:48:47 2011 UTC (2 years, 5 months ago) by jmmv
Branches: MAIN
CVS tags: HEAD
Define the per-project category and difficulty at the template level,
instead of manually tagging the project pages.  While doing this, prefix
the tags with "category:" and "difficulty:" to make them easier to
understand.

[[!template id=project

title="Binary compatibility for puffs backend"

contact="""
[tech-kern](mailto:tech-kern@NetBSD.org), [tech-userlevel](mailto:tech-userlevel@NetBSD.org)
"""

mentors="""
[Antti Kantee](mailto:pooka@NetBSD.org)
"""

category="kernel"
difficulty="medium"
duration="3 months"

description="""
Currently, the [puffs(3)](http://netbsd.gw.com/cgi-bin/man-cgi?puffs+3+NetBSD-5.1+i386) interface between the kernel and userspace uses various system structures for passing information. Examples are `struct stat` and `struct uucred`. If these change in layout (such as with the recent time_t size change), old puffs servers must be recompiled.

The purpose of the project is to:

* *define* a binary-independent protocol
* *implement* support
* *measure* the performance difference with direct kernel struct passing
* if there is a huge difference, *investigate* the possibility for having both an internal and external protocol. The actual decision to include support will be made on the relative complexity of the code for dual support.

While this project will be partially implemented in the kernel, it is fairly well-contained and prior kernel experience is not necessary.

If there is time and interest, a suggested subproject is making sure that [p2k(3)](http://netbsd.gw.com/cgi-bin/man-cgi?p2k+3+NetBSD-5.1+i386) does not suffer from similar issues. This is a required subproject if dual support as mentioned above is not necessary.
"""
]]

[[!tag gsoc]]

CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb