Changes

37 bytes added ,  14:00, 18 October 2012
no edit summary
Line 14: Line 14:  
| crtools || Modify restored resources run-time || xemul@ || Need (probably) some way to alter what is being restored. Usage example -- change the IP address of sockets from task above.
 
| crtools || Modify restored resources run-time || xemul@ || Need (probably) some way to alter what is being restored. Usage example -- change the IP address of sockets from task above.
 
|-
 
|-
| crtools/kernel || madvise bits || - || currently we just drop these bits, since we have no API to find them out on dump
+
| crtools/kernel || madvise bits || gorcunov@ || currently we just drop these bits, since we have no API to find them out on dump
 
|-
 
|-
 
| crtools || partial migration || - || migrate some tasks while proxying IPC to existing others (pipes->sockets, etc.)
 
| crtools || partial migration || - || migrate some tasks while proxying IPC to existing others (pipes->sockets, etc.)
Line 44: Line 44:  
| vzkernel/crtools || OpenVZ kernel support || - || Within 3.5 and RHEL7 port
 
| vzkernel/crtools || OpenVZ kernel support || - || Within 3.5 and RHEL7 port
 
|-
 
|-
| crtools || More sockoptions || - || -
+
| crtools || More sockoptions || xemul@ || SOL_ are mostly done
 
|-
 
|-
 
| crtools || Bridges in container || - ||
 
| crtools || Bridges in container || - ||
Line 58: Line 58:  
| crtools || file locks || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?
 
| crtools || file locks || - || It's hard to do it carefully. We need to make sure that all lock users are taken into dump. Only support it inside container?
 
|-
 
|-
| kernel || unhashed sockets || - || When we create a tcp socket it doesn't get to eny hashes and is not reported by diag infra. However, there exists stuff that we can configure on such a socket and there's no existing APIs for getting this info (e.g. -- bind to device). What to do? Report unhashed sockets with diag or extend API for this crap?
+
| kernel || unhashed sockets || xemul@ || When we create a tcp socket it doesn't get to eny hashes and is not reported by diag infra. However, there exists stuff that we can configure on such a socket and there's no existing APIs for getting this info (e.g. -- bind to device). What to do? Report unhashed sockets with diag or extend API for this crap?
 
|}
 
|}