Re: [Nbd] Question about the expected behaviour of nbd-server for async ops
Brought to you by:
yoe
From: Wouter V. <w...@ut...> - 2011-06-01 06:55:14
|
On Tue, May 31, 2011 at 08:07:42AM -0400, Paul Clements wrote: > On Mon, May 30, 2011 at 11:14 AM, Alex Bligh <al...@al...> wrote: > > > > > > --On 30 May 2011 14:13:04 +0200 Goswin von Brederlow <gos...@we...> > > 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. I am not aware of any current limit > > on the size of a request (other than 2^32 bytes). > > nbd limits requests to 127KB: > > /sys/block/nbd0/queue/max_hw_sectors_kb:127 Has this always been the case? If so, there appears to be something wrong where it does not limit requests to that size. -- The volume of a pizza of thickness a and radius z can be described by the following formula: pi zz a |