public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Steve Whitehouse <Steve@ChyGwyn.com>
Cc: Luc Robalo Marques <robalomarquesl@yahoo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: nbd request too big
Date: Fri, 11 Jan 2002 23:36:22 +0000	[thread overview]
Message-ID: <20020111233621.D260@toy.ucw.cz> (raw)
In-Reply-To: <20020107152423.78321.qmail@web14906.mail.yahoo.com> <200201071538.PAA28211@gw.chygwyn.com>
In-Reply-To: <200201071538.PAA28211@gw.chygwyn.com>; from steve@gw.chygwyn.com on Mon, Jan 07, 2002 at 03:38:29PM +0000

Hi!

> I presume you are using Pavel's server from his web page ? You need to increase
> the buffer size that the server uses. This happens as a result of the change
> a little while ago of nbd to use the elevator to merge requests at the nbd
> client end. If memory serves the maximum size of request is sizeof(header) +
> 128 * block_size, so you need to alter the server to use that size.
> 
> You'll find the buffer size in the main loop of the mainloop() function
> char buf[20480]; needs increasing (to (131072 + 28) for 1k blocks for example)
> and also you'll need to increase the value here (to 131072 in this example):
> 
>                 if (len > 10240)
>                         err("Request too big!");

Thanx for explanation and would-be patch. I'll apply it into CVS.

Perhaps have acount on sourceforge and you want write access to the CVS?

								Pavel
-- 
Philips Velo 1: 1"x4"x8", 300gram, 60, 12MB, 40bogomips, linux, mutt,
details at http://atrey.karlin.mff.cuni.cz/~pavel/velo/index.html.


  reply	other threads:[~2002-01-18 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-07 15:24 nbd request too big Luc Robalo Marques
2002-01-07 15:38 ` Steven Whitehouse
2002-01-11 23:36   ` Pavel Machek [this message]
2002-01-07 17:53 ` Paul Clements
2002-01-11 21:19   ` 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=20020111233621.D260@toy.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Steve@ChyGwyn.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robalomarquesl@yahoo.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