[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-admin
Subject:    Re: Kernel read/write Blocksize
From:       Glynn Clements <glynn () gclements ! plus ! com>
Date:       2006-12-07 12:21:18
Message-ID: 17784.1854.73445.28255 () cerise ! gclements ! plus ! com
[Download RAW message or body]


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 <glynn@gclements.plus.com>
-
To unsubscribe from this list: send the line "unsubscribe linux-admin" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
[prev in list] [next in list] [prev in thread] [next in thread]