Hi,
I'm writing documentation about the VFS. More concretely, I want to
document the following information about the methods defined in the
VFS interface (i.e. the struct *_operations):
- Prototype.
- Description (brief description of what the method has to do).
- Description of the pa
Hi,
I continue studying the VFS interface. As I said in previous e-mails,
my goal is to integrate an existing parallel filesystem into the Linux
kernel.
Now, I am looking for a reduced subset of operations to focus on. I
have selected the following:
struct file_system_type
get_sb()
struct
Hi,
As I anounced a couple of weeks ago, I'm studying how to build a new
filesystem. I have taken a look at the ramfs and also read some
documentation about.
Now I'm writing my own dummyfs (based on ramfs) to know how this
works, but I'm having problems compiling it; I need to include the
"linux/
Hi,
I have a piece of code which uses environment variables. I have been
told that it is not going to work in kernel space because the concept
of environment is not applicable inside the kernel.
I belive that, but I need to demonstrate it. I do not know how to
proof this, perhaps referring to a s
Whoa!, I did not expect so many replies. Thank you for your answers.
The thing is that the Computer Architecture area of the University I
am studying at is developing a parallel filesystem. Currently it works
as a stand-alone program (this is why it uses resources like
environment variables), and
> On Friday 19 August 2005 01:12, Alan Cox wrote:
> ---[ 8< ]-
> > Essentially environment is user space business and you can't get at it
> > from the kernel.
> -[ 8< ]
>
> I think the OP has his answer here. If someone knows what he is talking about,
> it's Ala
On 8/22/05, Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> ??
> Usually when I hear stand-alone program I think of program that runs
> without the need of a kernel. You have an environment in that context?
Without the need of a kernel? Perhaps I did not explain myself
correctly... I meant a user
> Just a bit of food for thought. There seem to be two different kinds
> of workloads for non-local filesystems. Bandwidth intensive workloads
> where files are read and written. Cache intensive workloads (like
> kernel compiles) where performance directly relates to how
> efficiently you can ma
8 matches
Mail list logo
