Re: Kernel read/write Blocksize

Neal Morrison wrote:

> > > So my question is: Is the stacksize simular to the read/write size? 
> > 
> > What do you mean by "read/write size"?
> 
> For example. I have to write an Server in C. And now I want to figure
> out which is the best blocksize, relative to the kernel, I should read
> from the socket. Is it easier for the kernel, when I read 4k blocks
> from the networkbuffer or doesn't matter?
> 
> I want to write the serverprogramm in relative to have the best
> performance, so I think that is fundamental to know something about the
> internel copy prozessing of the kernel.

For networking, it doesn't matter.

Block size is more relevant for disk I/O, particularly for memory
mapped I/O (mmap() etc), and to a lesser extent for random access
(lseek() etc).

-- 
Glynn Clements <[email protected]>