From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Michael Holzheu <HOLZHEU@de.ibm.com>
Cc: linux-kernel@vger.kernel.org, mschwid2@de.ibm.com, penberg@gmail.com
Subject: Re: [PATCH/RFC] s390: Hypervisor File System
Date: Fri, 21 Apr 2006 18:38:18 +0300 [thread overview]
Message-ID: <1145633898.13191.9.camel@localhost> (raw)
In-Reply-To: <OF5500FC25.13788C4B-ON42257157.004C98F0-42257157.004DB206@de.ibm.com>
Hi Michael,
On Fri, 2006-04-21 at 16:08 +0200, Michael Holzheu wrote:
> The first one was, that the hardware interface for getting the data is
> very expensive. We always get back the data for all LPARs and all
> cpus. Therefore we do not want to get the data every time an attribute
> file is read.
You can cache the results in userspace. So I don't see this one as an
argument for making the kernel more complex.
On Fri, 2006-04-21 at 16:08 +0200, Michael Holzheu wrote:
> The second problem was, that we want to provide a consistent snapshot
> of the hypervisor data for the user space application.
How do you ensure consistency now? And how is that different from an
userspace process reading the whole directory hierarchy into cache in
one go?
The update-on-write to special file thing seems bit strange to me. What
if two processes ask for it at the same time?
Pekka
next prev parent reply other threads:[~2006-04-21 15:45 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 11:35 [PATCH/RFC] s390: Hypervisor File System Michael Holzheu
2006-04-21 11:53 ` Pekka Enberg
2006-04-21 13:56 ` Michael Holzheu
2006-04-21 14:55 ` Arnd Bergmann
2006-04-21 15:31 ` Michael Holzheu
2006-04-21 13:32 ` Pekka Enberg
2006-04-21 14:08 ` Michael Holzheu
2006-04-21 15:38 ` Pekka Enberg [this message]
2006-04-21 16:40 ` Martin Schwidefsky
2006-04-25 14:04 ` Pekka Enberg
2006-04-21 14:42 ` Pekka Enberg
2006-04-21 14:59 ` Michael Holzheu
2006-04-21 15:41 ` Pekka Enberg
2006-04-21 15:18 ` Jörn Engel
2006-04-21 15:36 ` Michael Holzheu
2006-04-21 15:46 ` Jörn Engel
2006-04-21 22:30 ` Ingo Oeser
2006-04-24 17:17 ` Michael Holzheu
2006-04-24 19:57 ` Ingo Oeser
2006-04-25 6:27 ` Pekka Enberg
2006-04-24 17:19 ` Michael Holzheu
-- strict thread matches above, loose matches on Subject: below --
2006-04-24 17:19 Michael Holzheu
2006-04-25 6:58 ` Pekka Enberg
2006-04-25 7:32 ` Pekka Enberg
2006-04-25 7:47 ` Andrew Morton
2006-04-25 8:01 ` Pekka Enberg
2006-04-25 8:52 ` Jörn Engel
2006-04-25 9:00 ` Pekka Enberg
2006-04-25 12:22 ` Michael Holzheu
2006-04-25 14:33 ` Pekka Enberg
2006-04-25 14:45 ` Jörn Engel
2006-04-26 9:30 ` Michael Holzheu
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=1145633898.13191.9.camel@localhost \
--to=penberg@cs.helsinki.fi \
--cc=HOLZHEU@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschwid2@de.ibm.com \
--cc=penberg@gmail.com \
/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