Hi folks, while working on portmap, I was thinking about moving the entire mapping table to the filesystem: one file per record. Benefits: * allows much simpler code: no internal maptable and load/store logic - just simple file IO (even limited to REST) * external programs can directly manipulate the map db, w/o goint through portmap itself * several portmap's (eg. for serving on separate sockets or different security domains) can easily share the same map. * less process memory consumption of portmap (on larger maps) Drawbacks: * a bit slower, more IO traffic * we have to rethink chroot'ing What do you think about this ? cu -- --------------------------------------------------------------------- Enrico Weigelt == metux IT service - http://www.metux.de/ --------------------------------------------------------------------- Please visit the OpenSource QM Taskforce: http://wiki.metux.de/public/OpenSource_QM_Taskforce Patches / Fixes for a lot dozens of packages in dozens of versions: http://patches.metux.de/ --------------------------------------------------------------------- -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
