From: Paul Clements <Paul.Clements@SteelEye.com>
To: "Pavel Machek" <pavel@suse.cz>, "Sven Köhler" <skoehler@upb.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [NBD] patch and documentation
Date: Mon, 08 Sep 2003 20:47:50 -0400 [thread overview]
Message-ID: <3F5D2336.A1AF2EBF@SteelEye.com> (raw)
In-Reply-To: 20030908232824.GH429@elf.ucw.cz
Pavel Machek wrote:
>
> Hi!
>
> > >>Another idea would be to be abled to specify the max_sectors while
> > >>connecting an NBD. That would add an optional paramter to the nbd-client
> > >>command line. (like it is possible for the blocksize)
> > >
> > >I do not see why it should be configurable...
> >
> > We may regret to use a certain value, although i agree that 1MB should
> > be sufficient for the future.
>
> I believe that 1MB is good, and good enough for close future. If that
> ever proves to be problem, we can add handshake at that point. But I
> do not believe it will be neccessary.
But, who ever said the buffer in the nbd-server had to be statically
allocated? I have a version of nbd-server that is modified to handle any
size request that the client side throws at it -- if the buffer is not
large enough, it simply reallocates it.
--
Paul
next prev parent reply other threads:[~2003-09-09 0:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 16:59 [NBD] patch and documentation Sven Köhler
2003-09-08 19:38 ` Pavel Machek
2003-09-08 19:42 ` Sven Köhler
2003-09-08 20:04 ` Paul Clements
2003-09-08 20:17 ` Sven Köhler
2003-09-08 21:10 ` Paul Clements
2003-09-08 22:04 ` Sven Köhler
2003-09-08 22:17 ` Pavel Machek
2003-09-08 22:13 ` Sven Köhler
2003-09-08 22:21 ` Pavel Machek
2003-09-08 22:24 ` Sven Köhler
2003-09-08 23:28 ` Pavel Machek
2003-09-09 0:12 ` Sven Köhler
2003-09-09 0:47 ` Paul Clements [this message]
2003-09-09 0:52 ` Sven Köhler
2003-09-09 6:10 ` Sven Köhler
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=3F5D2336.A1AF2EBF@SteelEye.com \
--to=paul.clements@steeleye.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=skoehler@upb.de \
/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