From: Neal Morrison <webmaster@nams.de>
To: linux-newbie@vger.kernel.org
Subject: Kernel read/write Blocksize
Date: Thu, 7 Dec 2006 11:23:20 +0100 [thread overview]
Message-ID: <20061207112320.38bfc62a@localhost.localdomain> (raw)
Hello everybody,
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
So my question is: Is the stacksize simular to the read/write size?
And what ist the best read/write size when I build my
own networkingprogramms?
--
Regards Neal
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next reply other threads:[~2006-12-07 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 10:23 Neal Morrison [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2006-12-07 12:21 ` Glynn Clements
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=20061207112320.38bfc62a@localhost.localdomain \
--to=webmaster@nams.de \
--cc=linux-newbie@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.