From: Steven Whitehouse <steve@gw.chygwyn.com>
To: aia21@cam.ac.uk (Anton Altaparmakov)
Cc: linux-kernel@vger.kernel.org, pavel@suse.cz,
linux-fsdevel@vger.kernel.org
Subject: Re: NBD client/server broken?
Date: Sun, 24 Mar 2002 20:16:38 +0000 (GMT) [thread overview]
Message-ID: <200203242016.UAA05010@gw.chygwyn.com> (raw)
In-Reply-To: <5.1.0.14.2.20020324183746.0452cec0@pop.cus.cam.ac.uk> from "Anton Altaparmakov" at Mar 24, 2002 06:46:11 PM
Hi,
>
> Just to keep interested parties informed:
>
> Thanks to Steven Whitehouse I found out that the latest nbd client/server
> user space programs are in CVS on Sourceforge (the kernel nbd documentation
> needs updating to point to http://sf.net/projects/nbd)...
>
> And I have just submitted a patch to Steven to make the nbd-server 64-bit
> clean on 32-bit machines and to allow proper auto detection of device size.
> Hopefully we will see it entering the CVS soon. Otherwise patch is
> available on request from me. (-:
>
Its all there now and as you suggested I've added the configure script so
autoconf is no longer required to build it.
> Mounting a NTFS 15GiB partition over nbd (using ntfs tng driver) gave me a
> data throughput of 7-10MiB/sec over 100MBit ethernet (going via switch and
> a hub) which is quite impressive. (-:
>
Also there is the zerocopy nbd patch I did for my UKUUG talk last year on my
patches page: http://www.chygwyn.com/~steve/kpatch/ its out of date now
but my plan is to update and sumbit it for 2.5 in the next few weeks or so.
It should make things even faster or at least more efficient if we are maxing
out the network already :-)
Steve.
next prev parent reply other threads:[~2002-03-24 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-24 13:10 NBD client/server broken? Anton Altaparmakov
2002-03-24 18:46 ` Anton Altaparmakov
2002-03-24 20:16 ` Steven Whitehouse [this message]
2002-03-25 0:48 ` Anton Altaparmakov
2002-03-25 11:18 ` Pavel Machek
2002-03-25 11:00 ` Steven Whitehouse
2002-03-25 11:13 ` Pavel Machek
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=200203242016.UAA05010@gw.chygwyn.com \
--to=steve@gw.chygwyn.com \
--cc=Steve@ChyGwyn.com \
--cc=aia21@cam.ac.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.