Hello-- On Mon, 2004-04-19 at 08:00, 林 松涛 wrote:> But there is a daemon(acceptor)compiled in userspace,listennig to > port 988. From the result of command "netstat -ap", every client make > some connections to mds by connecting to 988. > > Does the daemon (acceptor) accepting connection requests for socknal > modules?It does, yes.> If i am right? Why not do it in kernel space such as scheduler or > reaptor?Only because it was the fastest way to do what we needed at the time, and we haven''t had a need to "fix" it. It would also work to listen from the kernel. -Phil
hi, Lustre use the NAL to run on different networks.I read the code of the socknal, there is no code for the "accept" ,which is a basic step for an "tcp" daemon.I just see there are three kind of daemons in socknal: scheduler,autoconnectted and reaptor. But there is a daemon(acceptor)compiled in userspace,listennig to port 988. From the result of command "netstat -ap", every client make some connections to mds by connecting to 988. Does the daemon (acceptor) accepting connection requests for socknal modules? If i am right? Why not do it in kernel space such as scheduler or reaptor? Thanks for any suggestions SongtaoL _________________________________________________________________ ÓëÁª»úµÄÅóÓѽøÐн»Á÷£¬ÇëʹÓà MSN Messenger: http://messenger.msn.com/cn