Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

modularity #35

Open
justincormack opened this issue Apr 27, 2013 · 0 comments
Open

modularity #35

justincormack opened this issue Apr 27, 2013 · 0 comments

Comments

@justincormack
Copy link
Owner

The code is getting bigger, and is only partially modular.

For many applications that does not matter as it is not huge at all. It will grow a little, but pretty much all the syscalls are in now.

There are a lot more functions and types that appear in other interfaces, such as ioctl, netlink etc, that are not used directly by syscalls. I think I will move these so they are only pulled in when you pull the relevant code, so types, constants are defined eg when you pull in eg the netlink code.

This means util should probably be split, and ioctl.

modules:

netlink which would pull in syscall.nl.types syscall.nl.constants etc
bridge (moved from util.bridge) which pulls in syscall.bridge.ioctl syscall.bridge.constants

In theory all of ioctl can move to these modules, although there will be a core for defining _IOW etc.

Other modules: tuntap, fuse etc

Tests should be split too.

This will leave a fixed size core syscall part which will stop growing. This could be further broken down.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant