linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Andreas Haumer <andreas@xss.co.at>
Cc: Rik van Riel <riel@conectiva.com.br>,
	Pavel Machek <pavel@suse.cz>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Bulent Abali <abali@us.ibm.com>,
	"Dirk W. Steinberg" <dws@dirksteinberg.de>,
	Ingo Oeser <ingo.oeser@informatik.tu-chemnitz.de>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: Swapping for diskless nodes
Date: Fri, 17 Aug 2001 23:25:06 +0200	[thread overview]
Message-ID: <20010817232506.B19037@atrey.karlin.mff.cuni.cz> (raw)
In-Reply-To: <3B7CBCD0.CD209D84@xss.co.at>; from andreas@xss.co.at on Fri, Aug 17, 2001 at 08:42:24AM +0200

Hi!

> > On Thu, 16 Aug 2001, Pavel Machek wrote:
> > 
> > > I'd call that configuration error. If swap-over-nbd works in all but
> > > such cases, its okay with me.
> > 
> > Agreed. I'm very interested in this case too, I guess we
> > should start testing swap-over-nbd and trying to fix things
> > as we encounter them...
> > 
> We do "testing" swap-over-nbd for some time now... :-))
> 
> In fact, all our workstations in our office are xS+S Diskless Clients, 
> and about 50 Diskless Clients are running at several customer sites.
> 
> In order to make Pavel happy :-) we did some more stress testing
> now, and here are the results:

Pavel is happy ;-).

> We set up a quite old machine (ASUS P55T2P4 motherboard,
> 64MB RAM, AMD K6/200 CPU, Matrox Millenium II graphics card,
> RTL8139 100MBit Ethernet) as Diskless Client with NBD Swap.
> 
> We installed our up-coming BLD-3.1 with Linux-2.2.19 kernel,
> Etherboot+initrd, DevFS and NBD swap patches.

Can you revert NBD swap patch and try again? It should break. If it
does not break, your testing is not good enough.
								Pavel
-- 
The best software in life is free (not shareware)!		Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

  reply	other threads:[~2001-08-17 21:25 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-09 14:26 Bulent Abali
2001-08-09 15:13 ` Alan Cox
2001-08-09 20:57   ` Rik van Riel
2001-08-09 22:46     ` Alan Cox
2001-08-11  1:16       ` Pavel Machek
2001-08-11  1:13   ` Pavel Machek
2001-08-14 12:57     ` Alan Cox
2001-08-16 21:46       ` Pavel Machek
2001-08-17  0:46         ` Rik van Riel
2001-08-17  1:35           ` Jakob Østergaard
2001-08-17 21:23             ` Pavel Machek
2001-08-17  6:42           ` Andreas Haumer
2001-08-17 21:25             ` Pavel Machek [this message]
2001-08-17 21:03           ` Andreas Haumer
2001-08-17 22:31             ` Dirk W. Steinberg
     [not found] <no.id>
     [not found] ` <E15Ulnx-0006zZ-00@the-village.bc.nu>
2001-08-09 10:50   ` Ingo Oeser
2001-08-09 13:12     ` Dirk W. Steinberg
2001-08-09 20:47     ` Rik van Riel
2001-08-09 15:19 ` Alan Cox
2001-08-09 17:09   ` Eric W. Biederman
2001-08-09 20:58     ` Rik van Riel
2001-08-10  8:11       ` Eric W. Biederman

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=20010817232506.B19037@atrey.karlin.mff.cuni.cz \
    --to=pavel@suse.cz \
    --cc=abali@us.ibm.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andreas@xss.co.at \
    --cc=dws@dirksteinberg.de \
    --cc=ingo.oeser@informatik.tu-chemnitz.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=riel@conectiva.com.br \
    /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