From mboxrd@z Thu Jan 1 00:00:00 1970 From: Glynn Clements Subject: Re: Kernel read/write Blocksize Date: Thu, 7 Dec 2006 12:21:18 +0000 Message-ID: <17784.1854.73445.28255@cerise.gclements.plus.com> References: <20061207111247.52bc6899@localhost.localdomain> <17783.60819.118509.714519@cerise.gclements.plus.com> <20061207120019.45d87d0f@localhost.localdomain> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20061207120019.45d87d0f@localhost.localdomain> Sender: linux-admin-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: Neal Morrison Cc: linux-admin@vger.kernel.org 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