Re: [Nbd] Question about the expected behaviour of nbd-server for async ops
- To: Alex Bligh <alex@...872...>
- Cc: nbd-general@lists.sourceforge.net
- Subject: Re: [Nbd] Question about the expected behaviour of nbd-server for async ops
- From: Wouter Verhelst <w@...112...>
- Date: Mon, 30 May 2011 17:36:29 +0200
- Message-id: <20110530153629.GA31747@...510...>
- In-reply-to: <462585F1D4B5526B79791BDA@...873...>
- References: <87oc2m28o7.fsf@...860...> <6DBA2A6208847F844397DB62@...873...> <87wrh9bz0c.fsf@...860...> <20110529120632.GB31747@...510...> <87tycdwp50.fsf@...860...> <20110529183212.GI31747@...510...> <87oc2k8orr.fsf@...860...> <20110530113649.GX31747@...510...> <877h988jzj.fsf@...860...> <462585F1D4B5526B79791BDA@...873...>
On Mon, May 30, 2011 at 04:14:46PM +0100, Alex Bligh wrote:
>
>
> --On 30 May 2011 14:13:04 +0200 Goswin von Brederlow <goswin-v-b@...186...>
> wrote:
>
> >> I don't think that not supporting extremely large requests is going to
> >> be a problem in practice, providing we return a proper error code.
> >
> > Maybe there should be an option field for this so client and server can
> > agree on a reasonable size. The client MUST then split larger requests
> > into smaller chunks.
>
> Note you will need to fix the kernel module (I think) if you want to limit
> the maximum size of a request.
Correct.
> I am not aware of any current limit on the size of a request (other
> than 2^32 bytes).
--
The volume of a pizza of thickness a and radius z can be described by
the following formula:
pi zz a
Reply to: