tech-kern archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Splitting the compat module?
In case anyone is unceratin about what I am referencing, this is what
I'm planning to make newly modular.
options SYSVMSG # System V-like message queues
options SYSVSEM # System V-like semaphores
options SYSVSHM # System V-like memory sharing
The compat code which is currently part of module/compat is in these
source files in src/sys/compat/common/
sysv_msg_14.c sysv_sem_14.c sysv_shm_14.c
sysv_msg_50.c sysv_sem_50.c sysv_shm_50.c sysv_ipc_50.c
On Tue, 5 May 2015, Paul Goyette wrote:
Folks,
The next modularization task I plan to attack is the SYSV_* options.
But first, I need to separate the SYSV* compat syscalls out of the
"standard" compat module, and into a separate module. Otherwise,
anything that requires any compat functionality will bring in all of
a new SYSV* module, even if none of the SYSV* code is needed.
I have not yet decided if the SYSV_* compat code should live in its own
module, or if it should be included in the "current" SYSV_* module.
Any comments or objections (preferably with alternatives)?
-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
-------------------------------------------------------------------------
-------------------------------------------------------------------------
| Paul Goyette | PGP Key fingerprint: | E-mail addresses: |
| (Retired) | FA29 0E3B 35AF E8AE 6651 | paul at whooppee.com |
| Kernel Developer | 0786 F758 55DE 53BA 7731 | pgoyette at netbsd.org |
-------------------------------------------------------------------------
Home |
Main Index |
Thread Index |
Old Index