Subject: Re: Heads up, kernel changes
To: Andrew Doran <ad@netbsd.org>
From: Adam Hamsik <haaaad@gmail.com>
List: current-users
Date: 07/11/2007 09:45:55
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


On Jul 9, 2007, at 11:23 PM, Andrew Doran wrote:

> Hi,
>
> I just committed a bunch of changes from the vmlocking branch to =20
> the kernel.
> Most of them are fairly mechanical changes after modifications to =20
> the kernel
> APIs for callouts, kthreads and device access. I don't expect major =20=

> upheaval
> but undoubtedly there will be some fallout as the changes were fairly
> extensive.21	=A7=09
I'm curious about how your changes (merged and unmerged vmlocking =20
branch) impact performance on SMP machines.
I think that these changes are mostly positive :), but I'm not sure.

>
> The only visible change should be that kthreads no longer get a =20
> process each
> but are now threads within process 0 (formerly the swapper). To see =20=

> them you
> need 'ps axs' or 'top -t'.
>
> Thanks,
> Andrew
>
> # ps ax
>   PID TTY   STAT    TIME COMMAND
>     0 ?     DKsl 0:00.00 [system]
>     1 ?     Ss   0:00.00 init
>   105 ?     Ss   0:00.00 /usr/sbin/syslogd -s
>   126 ?     Isl  0:00.00 /usr/sbin/named
>   134 ?     Ss   0:00.00 /usr/sbin/rpcbind -l
>   148 ?     Ss   0:00.00 mount_mfs -s 532224 /dev/wd1b /tmp
>   267 ?     Ss   0:00.00 /usr/sbin/ntpd
>   285 ?     Is   0:00.00 /usr/sbin/sshd
>   337 ?     Is   0:00.00 /usr/sbin/inetd -l
>   338 ?     Ss   0:00.00 /usr/sbin/cron
>   365 ?     S    0:00.00 sshd: ad@ttyp0
>   366 ?     Is   0:00.00 sshd: ad [priv]
>   360 ttyp0 Ss   0:00.00 -ksh
>  9626 ttyp0 S    0:00.00 ksh
> 29064 ttyp0 R+   0:00.00 ps -ax
>   373 tty00 Is+  0:00.00 /usr/libexec/getty Pc console
> #

Regards
- -----------------------------------------
Adam Hamsik
jabber: haad@jabber.org
icq: 249727910

Proud NetBSD user.

We program to have fun.
Even when we program for money, we want to have fun as well.
~ Yukihiro Matsumoto




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)

iD8DBQFGlIqzlIxPgX3Go0MRAnaiAJ0SWbEBD4Gr+9php417+kLyGSEi2ACggOL/
lS3RD4H0oeGRvRMoPGZWt6Y=3D
=3DtUUn
-----END PGP SIGNATURE-----