Hi, Folks,. from this moment, I be in this list, for learning how can help to NetBSD project into docs, and more, my personal web page is: http://bsdguy.net and at this moment only spanish is available, i promise do it in english, I suspect help too project . Regards. Fco. Valladolid
Hi, nice to see you here! And welcome to netbsd-docs ;) On Mon, Oct 04, 2004 at 09:28:31PM +0000, Fco. Valladolid wrote: > Hi, Folks,. from this moment, I be in this list, for learning how can help to NetBSD > project into docs, and more, my personal web page is: http://bsdguy.net and at this moment only > spanish is available, i promise do it in english, I suspect help too project . > > Regards. > > Fco. Valladolid Sincerely, Simas Mockevicius -- http://www.NetBSD.org/ - run with it!
http://www.netbsd.org/gallery/articles.html#krause-bsdtodayA The links to this articles is broken. Regards.
On Tue, 5 Oct 2004, Fco. Valladolid wrote: > http://www.netbsd.org/gallery/articles.html#krause-bsdtodayA > > The links to this articles is broken. I designed and managed BSD Today for two years. After I left a couple years ago, the site died. We probably should not link to the BSD Today articles since the site has been gone for over a year. We also might want to ask Ralph Krause for reuse or to link to his articles elsewhere. He wrote the articles for me four years ago so they may be out-of-date though. (I do have originals but I don't have permission to publish them.) Jeremy C. Reed BSD News, BSD tutorials, BSD links http://www.bsdnewsletter.com/ p.s. I need to work on the above too :)
[because I'm not subscribing netbsd-docs, please Cc: to me, if you have any comments to this post] I have some comments about the following page: http://www.netbsd.org/guide/en/chap-whatsnew.html (Chapter,A (B2.,A (BNew features in NetBSD 2.0) > 2.1.1.,A (BNative threads > multiple threads within the same process can run concurrently on > different CPUs It's worth mentioning that one needs to set $PTHREAD_CONCURRENCY environment to the number of CPUs to make it actually run on multiple CPUs on NetBSD 2.0. Especially because there is no existing common practice about this environment variable on other OS, and this may be a temporary measure. (If our implementation is mature enough, the pthread library must set $PTHREAD_CONCURRENCY to the number of CPUs by default.) Also, there are some other topics which are worth mentioning. e.g. 1. old buffer cache, which is used to cache filesystem metadata (e.g. directories, i-nodes), are now dynamically allocated. The old buffer cache now can use up to 15% of phyisical memory by default. On machines which only have really small memory, it may be better to limit this upper bound by e.g. "sysctl -w vm.bufcache=5".(Continue reading)
On Tue, Oct 12, 2004 at 11:39:58PM +0900, SODA Noriyuki wrote: > It's worth mentioning that one needs to set $PTHREAD_CONCURRENCY > environment to the number of CPUs to make it actually run on multiple > CPUs on NetBSD 2.0. Especially because there is no existing common > practice about this environment variable on other OS, and this may be > a temporary measure. > (If our implementation is mature enough, the pthread library > must set $PTHREAD_CONCURRENCY to the number of CPUs by default.) Good point. But I think it would not be a good idea to add this to chap-whatsnew as a showcase of new features. But I think it would be a very good idea to add this to chap-boot. > 1. old buffer cache, which is used to cache filesystem metadata > (e.g. directories, i-nodes), are now dynamically allocated. Ack. > The old buffer cache now can use up to 15% of phyisical memory > by default. > On machines which only have really small memory, it may be > better to limit this upper bound by e.g. "sysctl -w vm.bufcache=5". chap-boot? > 2. Many enhancements about user visible library functions. > e.g. native iconv(3), utmpx, SA_SIGINFO, POSIX 1003.1b semaphores, ... Ack.(Continue reading)
>>>>> On Tue, 12 Oct 2004 21:20:08 +0200, Daniel de Kok <danieldk <at> pobox.com> said: >> It's worth mentioning that one needs to set $PTHREAD_CONCURRENCY >> environment to the number of CPUs to make it actually run on multiple >> CPUs on NetBSD 2.0. Especially because there is no existing common >> practice about this environment variable on other OS, and this may be >> a temporary measure. >> (If our implementation is mature enough, the pthread library >> must set $PTHREAD_CONCURRENCY to the number of CPUs by default.) > Good point. But I think it would not be a good idea to add this to > chap-whatsnew as a showcase of new features. Hmm, yeah, that's right. It may be better to have a pointer to the description in chap-whatsnew, though. > But I think it would be a very good idea to add this to chap-boot. I think chap-boot isn't a right place to put this description, because I guess the intention to use the environment variable is to set this value per command basis. I'm not sure where is the good place to add the description, though. >> The old buffer cache now can use up to 15% of phyisical memory >> by default. >> On machines which only have really small memory, it may be >> better to limit this upper bound by e.g. "sysctl -w vm.bufcache=5".(Continue reading)
On Tue, 12 Oct 2004 14:39:58 +0000, SODA Noriyuki wrote: > [because I'm not subscribing netbsd-docs, please Cc: to me, > if you have any comments to this post] > > I have some comments about the following page: > http://www.netbsd.org/guide/en/chap-whatsnew.html This page should be kept in sync with the INSTALL document. There are some changes mentioned in the INSTALL document which are not found in the Guide and are quite important to some users, such as ipfilter on bridge or hostap mode on wireless interfaces. It also mentions some scalability improvements in network code. Sorry for repeating it, but is it really necessary to have this information duplicated? Keeping it in sync seems difficult. Bye Pavel
On Tue, Oct 12, 2004 at 09:50:01PM +0200, Pavel Cahyna wrote: > On Tue, 12 Oct 2004 14:39:58 +0000, SODA Noriyuki wrote: > > > [because I'm not subscribing netbsd-docs, please Cc: to me, > > if you have any comments to this post] > > > > I have some comments about the following page: > > http://www.netbsd.org/guide/en/chap-whatsnew.html > > This page should be kept in sync with the INSTALL document. There are some > changes mentioned in the INSTALL document which are not found in the Guide > and are quite important to some users, such as ipfilter on bridge or > hostap mode on wireless interfaces. It also mentions some scalability > improvements in network code. > > Sorry for repeating it, but is it really necessary to have this > information duplicated? Keeping it in sync seems difficult. In general, yes. Remember that there are/were plans to get the guide printed. And it would probably be good to have a fairly complete, so readers don't have to hunt for other documentation when they have it. But I have no strong opinions about this chapter. Maybe someone else? -- Daniel
On Tue, Oct 12, 2004 at 11:39:58PM +0900, SODA Noriyuki wrote: > 1. old buffer cache, which is used to cache filesystem metadata > (e.g. directories, i-nodes), are now dynamically allocated. > > 3. Many scalability improvements. e.g. rbtree vmmap, splay tree > pvtree on i386 pmap, O(C) data insertion into socket buffers, etc... > (c.f. http://bulk.fefe.de/scalability/) How about this? ftp://ftp.netbsd.org/pub/NetBSD/misc/daniel/patches/chap-whatsnew.xml.diff -- Daniel
RSS Feed2 | |
|---|---|
7 | |
8 | |
10 | |
2 | |
7 | |
5 | |
4 | |
23 | |
14 | |
4 | |
4 | |
6 | |
2 | |
1 | |
4 | |
9 | |
6 | |
10 | |
1 | |
2 | |
11 | |
1 | |
1 | |
4 | |
4 | |
4 | |
14 | |
1 | |
16 | |
5 | |
7 | |
14 | |
2 | |
2 | |
1 | |
1 | |
7 | |
10 | |
4 | |
1 | |
3 | |
4 | |
1 | |
17 | |
1 | |
3 | |
7 | |
9 | |
3 | |
19 | |
6 | |
3 | |
5 | |
10 | |
6 | |
3 | |
8 | |
14 | |
39 | |
139 | |
2 | |
4 | |
22 | |
37 | |
44 | |
17 | |
20 | |
17 | |
17 | |
19 | |
28 | |
44 | |
26 | |
36 | |
55 | |
31 | |
32 | |
55 | |
47 | |
36 | |
92 | |
37 | |
64 | |
67 | |
28 | |
9 | |
19 | |
27 | |
39 | |
34 | |
19 | |
21 | |
20 | |
5 | |
13 | |
32 | |
11 | |
53 | |
40 | |
46 | |
71 | |
11 | |
22 | |
21 | |
34 | |
30 | |
38 | |
13 | |
4 | |
30 | |
3 | |
8 | |
12 | |
13 | |
15 | |
9 | |
21 | |
15 | |
39 | |
1 | |
15 |
