Re: [Netnice-kernels] NNFS was: Re: Sourceforge Account

[Takashi O. <ta...@cs...>]

hi scott,

i still don't understand your question. but, i think it is a good
idea to try our bootable CD to know how it works. this is definitely
a better specification of the API, better than the simplified description
of the page you mentioned.

	http://www.netnice.org/download.cgi

i personally think the problem of NNFS on Linux is that we may not need
all of the features of linux-procfs (or, contents under /proc). this is
because, although i'm thinking to mount NNFS at /proc and thinking to provide
capability of linux-procfs, it might not be the best solution in respect
to the amount of coding we need. we may simply mount nnfs at /network
or somewhere else, not sticking to the procfs compatibility. so, that
is a open problem, and i'm happy to discuss the issue.

but, i don't think it is a right way, to create a file system which
contains just the directories under /proc/network of FreeBSD and
mount it under /proc/network of linux-procfs. we need to setup a lot
of links between process-dependent directories under /proc/PIDs and
VIF directories under /proc/network, and thus, they cannot be separated
that way, i believe.

i guess that the confusion is mostly coming from the difference of
organizations between FreeBSD-procfs and linux-procfs. and, maybe
it is a good idea to have a tele-conference to avoid further confusion.
we have a polycom system in my department, and i use MSN messenger
also (ta...@ho...).

i'm sorry that i'm not answering to all of questions, but, i believe
that it is a good starting point to try the working system first,
and then, to think how we realize a similar feature on Linux.

hope this helps, and i would apologize if you've already tried the
FreeBSD/Netnice.


-- taka

Scott Brumbaugh wrote:
>
> There is an illustration and text description under the heading 'File
> System Representation' .  Mounted directly under /proc is the nnfs
> network/ directory which holds the VIF interfaces themselves.  However
> under /proc are directories corresponding to the PIDs of running
> processes and under them are sockets/ directories that contain links
> to the VIF interfaces under network/.
> 
> I am new to this project so my understanding may be wrong, but to
> create this structure on linux my idea is to create the nnfs network/
> directory and mount it and then modify the existing /proc adding a
> sockets/ virtual directory under each PID and under each sockets/
> directory establish links to the VIF interface under network/ .
> 
> >From the text description on the web page I read:
> 
>     A directory under /proc/network/ represents a VIF. ...
> 
> Then, in the next paragraph:
> 
>     Directories under /proc/[pid]/ are process entries, as usual. We
>     added a sockets directory under each process entry. ...
> 
> On Linux, /proc/[pid] exists and it has been my intention to figure
> out if a sockets directory can be added under each one.  Now maybe
> this will not be possible due to the design of linux procfs but at
> this point I have not seen that it is not possible to create this
> sockets directory.
> 
> Now, from your response, I am reasoning that your approach here would
> be to copy the code from linux procfs that exposes the PIDS and put
> that code into the new nnfs thus creating a directory structure under
> the new nnfs that contains both the VIFS and the PIDs that are using
> the VIFS.  This structure is different from the illustration and the
> high level description of the API as far as I can tell.  However, I am
> just starting out here and trying to get up to speed quickly so I am
> perhaps rushing my understanding.