From: Arjan van de Ven <arjanv@redhat.com>
To: Lars Marowsky-Bree <lmb@suse.de>
Cc: Daniel Phillips <phillips@istop.com>,
sdake@mvista.com, David Teigland <teigland@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Minneapolis Cluster Summit, July 29-30
Date: Mon, 12 Jul 2004 14:01:27 +0200 [thread overview]
Message-ID: <20040712120127.GB16604@devserv.devel.redhat.com> (raw)
In-Reply-To: <20040712115003.GV3933@marowsky-bree.de>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
On Mon, Jul 12, 2004 at 01:50:03PM +0200, Lars Marowsky-Bree wrote:
>
> True enough, but I'm somewhat unhappy with this still. So whenever we
> have something like that we need to move it into the kernel space?
> (pvmove first, and now the clustering etc.) Can't we come up with a way
> to export this flag to user-space?
I'm not convinced that's a good idea, in that it exposes what is basically VM internals
to userspace, which then would become a set-in-stone interface....
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-07-12 12:03 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-05 6:09 [ANNOUNCE] Minneapolis Cluster Summit, July 29-30 Daniel Phillips
2004-07-05 15:09 ` Christoph Hellwig
2004-07-05 18:42 ` Daniel Phillips
2004-07-05 19:08 ` Chris Friesen
2004-07-05 20:29 ` Daniel Phillips
2004-07-07 22:55 ` Steven Dake
2004-07-08 1:30 ` Daniel Phillips
2004-07-05 19:12 ` Lars Marowsky-Bree
2004-07-05 20:27 ` Daniel Phillips
2004-07-06 7:34 ` Lars Marowsky-Bree
2004-07-06 21:34 ` Daniel Phillips
2004-07-07 18:16 ` Lars Marowsky-Bree
2004-07-08 1:14 ` Daniel Phillips
2004-07-08 9:10 ` Lars Marowsky-Bree
2004-07-08 10:53 ` David Teigland
2004-07-08 14:14 ` Chris Friesen
2004-07-08 16:06 ` David Teigland
2004-07-08 18:22 ` Daniel Phillips
2004-07-08 19:41 ` Steven Dake
2004-07-10 4:58 ` David Teigland
2004-07-10 4:58 ` Daniel Phillips
2004-07-10 17:59 ` Steven Dake
2004-07-10 20:57 ` Daniel Phillips
2004-07-10 23:24 ` Steven Dake
2004-07-11 19:44 ` Daniel Phillips
2004-07-11 21:06 ` Lars Marowsky-Bree
2004-07-12 6:58 ` Arjan van de Ven
2004-07-12 10:05 ` Lars Marowsky-Bree
2004-07-12 10:11 ` Arjan van de Ven
2004-07-12 10:21 ` Lars Marowsky-Bree
2004-07-12 10:28 ` Arjan van de Ven
2004-07-12 11:50 ` Lars Marowsky-Bree
2004-07-12 12:01 ` Arjan van de Ven [this message]
2004-07-12 13:13 ` Lars Marowsky-Bree
2004-07-12 13:40 ` Nick Piggin
2004-07-12 20:54 ` Andrew Morton
2004-07-13 2:19 ` Daniel Phillips
2004-07-13 2:31 ` Nick Piggin
2004-07-27 3:31 ` Daniel Phillips
2004-07-27 4:07 ` Nick Piggin
2004-07-27 5:57 ` Daniel Phillips
2004-07-14 12:19 ` Pavel Machek
2004-07-15 2:19 ` Nick Piggin
2004-07-15 12:03 ` Marcelo Tosatti
2004-07-14 8:32 ` Pavel Machek
2004-07-12 4:08 ` Steven Dake
2004-07-12 4:23 ` Daniel Phillips
2004-07-12 18:21 ` Steven Dake
2004-07-12 19:54 ` Daniel Phillips
2004-07-13 20:06 ` Pavel Machek
2004-07-12 10:14 ` Lars Marowsky-Bree
[not found] <fa.io9lp90.1c02foo@ifi.uio.no>
[not found] ` <fa.go9f063.1i72joh@ifi.uio.no>
2004-07-06 6:39 ` Aneesh Kumar K.V
-- strict thread matches above, loose matches on Subject: below --
2004-07-10 14:58 James Bottomley
2004-07-10 16:04 ` David Teigland
2004-07-10 16:26 ` James Bottomley
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=20040712120127.GB16604@devserv.devel.redhat.com \
--to=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lmb@suse.de \
--cc=phillips@istop.com \
--cc=sdake@mvista.com \
--cc=teigland@redhat.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