From: "Guillermo López Alejos" <glalejos@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Linh Dang <linhd@nortel.com>, linux-kernel@vger.kernel.org
Subject: Re: Environment variables inside the kernel?
Date: Thu, 25 Aug 2005 10:59:29 +0200 [thread overview]
Message-ID: <4fec73ca050825015970a57910@mail.gmail.com> (raw)
In-Reply-To: <m1r7cmtjm7.fsf@ebiederm.dsl.xmission.com>
> 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 make use of the page cache, and not get buried
> in cache contention.
Yes, those performance factors have to been taken in account. The
bandwith intensive workloads depends on the implementation of the
filesystem. Note that I am not involved in the internal details of
this filesystem, my goal is to integrate it in the Linux kernel.
The usage of cache memory in this distributed schemas is complicated.
Probably it will be necessary to implement protocols to ensure cache
coherency and consistency.
Hum... it seems that we are going away from environment variables :)
--
Guillermo
next prev parent reply other threads:[~2005-08-25 8:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-18 15:44 Environment variables inside the kernel? Guillermo López Alejos
2005-08-18 16:02 ` linux-os (Dick Johnson)
2005-08-18 16:03 ` jerome lacoste
2005-08-18 16:12 ` Ingo Oeser
2005-08-18 17:27 ` Christoph Lameter
2005-08-18 16:37 ` Douglas McNaught
2005-08-18 18:23 ` Linh Dang
2005-08-18 18:48 ` Guillermo López Alejos
2005-08-18 19:43 ` Emilio Jesús Gallego Arias
2005-08-21 22:12 ` Eric W. Biederman
2005-08-22 9:05 ` Guillermo López Alejos
2005-08-22 9:18 ` Eric W. Biederman
2005-08-25 8:59 ` Guillermo López Alejos [this message]
2005-08-22 20:38 ` Helge Hafting
2005-08-18 23:12 ` Alan Cox
2005-08-18 22:55 ` Peter M. Groen
2005-08-19 10:28 ` Guillermo López Alejos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4fec73ca050825015970a57910@mail.gmail.com \
--to=glalejos@gmail.com \
--cc=ebiederm@xmission.com \
--cc=linhd@nortel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox