From: Neal Morrison <webmaster@nams.de>
To: Glynn Clements <glynn@gclements.plus.com>
Cc: linux-admin@vger.kernel.org
Subject: Re: Kernel read/write Blocksize
Date: Thu, 7 Dec 2006 12:00:19 +0100 [thread overview]
Message-ID: <20061207120019.45d87d0f@localhost.localdomain> (raw)
In-Reply-To: <17783.60819.118509.714519@cerise.gclements.plus.com>
On Thu, 7 Dec 2006 10:31:47 +0000
Glynn Clements <glynn@gclements.plus.com> wrote:
>
> Neal Morrison wrote:
>
> > some of my colleagues told me that the internel Buffsize ist 4k.
> > Yesterday I saw in the Kernelconfigurations that the default value for
> > the stacksize is 8k and you can set it to 4k.
> >
> > Kernel hacking -> Use 4Kb for kernel stacks instead of 8Kb
>
> Note that this is for the kernel stack, not the user-space stack.
Ok, thank you for this clearing.
> > 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.
--
Regards Neal
P.S. Please excuse of my bad english.
next prev parent reply other threads:[~2006-12-07 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 10:12 Kernel read/write Blocksize Neal Morrison
2006-12-07 10:31 ` Glynn Clements
2006-12-07 11:00 ` Neal Morrison [this message]
2006-12-07 12:21 ` Glynn Clements
-- strict thread matches above, loose matches on Subject: below --
2006-12-07 10:23 Neal Morrison
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061207120019.45d87d0f@localhost.localdomain \
--to=webmaster@nams.de \
--cc=glynn@gclements.plus.com \
--cc=linux-admin@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.