Re: the virtual device management in eth-multiplexer

2009-03-06 Thread Zheng Da
On Fri, Mar 6, 2009 at 5:08 AM, wrote: > Hi, > > On Thu, Mar 05, 2009 at 04:10:13PM +, Zheng Da wrote: > > On Thu, Mar 5, 2009 at 2:23 AM, wrote: > > > > Can you make it to the meeting this friday? (It is rather urgent, as > > > I'm considering making a GSoC task out of it...) > > > > > I th

Re: the virtual device management in eth-multiplexer

2009-03-06 Thread olafBuddenhagen
Hi, On Thu, Mar 05, 2009 at 04:10:13PM +, Zheng Da wrote: > On Thu, Mar 5, 2009 at 2:23 AM, wrote: > > Can you make it to the meeting this friday? (It is rather urgent, as > > I'm considering making a GSoC task out of it...) > > > I think it will be OK. Let's meet at 7:00pm this Friday. By

Re: the virtual device management in eth-multiplexer

2009-03-05 Thread Zheng Da
Hi, On Thu, Mar 5, 2009 at 2:23 AM, wrote: > I thought more about it, and realized that perhaps storing the > configuration permanently is not such a bad idea after all -- it is > closely related to something I have considered in other contexts in the > past: namely permanently storing translato

Re: the virtual device management in eth-multiplexer

2009-03-04 Thread olafBuddenhagen
Hi, On Sun, Feb 08, 2009 at 09:48:47PM +0100, olafbuddenha...@gmx.net wrote: > On Sun, Feb 01, 2009 at 02:20:41AM +, Da Zheng wrote: > > so maybe it is better to give up the idea that the directory where > > eth-multiplexer sits is the place to show the status of devices and > > allow the cli

Re: the virtual device management in eth-multiplexer

2009-02-23 Thread olafBuddenhagen
Hi, On Sun, Feb 22, 2009 at 01:19:06PM +, Zheng Da wrote: > On Wed, Feb 18, 2009 at 8:33 PM, wrote: > but again, if nodes are created automatically, there will be some > strange behavior from the filesystem's point of view. for example, > "ls" can create an transitory node, or a user can cre

Re: the virtual device management in eth-multiplexer

2009-02-22 Thread Zheng Da
On Wed, Feb 18, 2009 at 8:33 PM, wrote: > > No, it's not! > > I explicitely said that the node is *not* discarded when it is still > used, i.e. when the device it represents is still open. It is only > discarded when there are *no* users anymore, i.e. neither references to > the node itself, nor t

Re: the virtual device management in eth-multiplexer

2009-02-19 Thread olafBuddenhagen
Hi, On Fri, Feb 13, 2009 at 08:50:39PM +, Da Zheng wrote: > olafbuddenha...@gmx.net wrote: >> The node should go away when it no longer has any users. When pfinet >> (or some other real user) uses a device, it will probably discard the >> port to the FS node (resulting from file_name_lookup()

Re: the virtual device management in eth-multiplexer

2009-02-13 Thread Da Zheng
Hi, olafbuddenha...@gmx.net wrote: Hi, On Sun, Feb 01, 2009 at 02:20:41AM +, Da Zheng wrote: In the current implementation, the device and the node associated to it are created when file_name_lookup() is called. when the last client closes the virtual device, the device is destroyed

Re: the virtual device management in eth-multiplexer

2009-02-08 Thread olafBuddenhagen
Hi, On Sun, Feb 01, 2009 at 02:20:41AM +, Da Zheng wrote: > In the current implementation, the device and the node associated to > it are created when file_name_lookup() is called. when the last > client closes the virtual device, the device is destroyed along with > the node. > > However,

the virtual device management in eth-multiplexer

2009-01-31 Thread Da Zheng
Hi, As antrik suggested, the virtual devices of eth-multiplexer are created dynamically. now there is an issue of management of virtual devices. eth-multiplexer is a netfs translator and the files in the directory on which it sits represent its virtual devices. At the beginning, I think the