On Tue, May 13, 2008 at 11:30:59AM +0300, Georgi Chorbadzhiyski wrote:
> >>http://mirrors.unixsol.org/slackware/slackware-12.1/kernels/hugesmp.s/config
> >>
> >
> >Your distro is building all of these modules into the kernel.
> > CONFIG_XFS_FS=y
> > CONFIG_JFS_FS=y
> > CONFIG_GFS2_FS=y
> >
> >This isnt exactly standard practice, normally they'd be set to =m and only
> >used if required to mount a filesystem. You may want to ask the slackware
> >people why they chose to do this for their hugexxx.s kernels.
>
> I know that they are compiled in the kernel, but since they
> are not used isn't starting their own kthreads kind of
> unnecessary? Surely the threads can be started on demand
> only when xfs/etc volume is mounted.
Sure - XFS will start another three kernel threads per filesystem
that gets mounted. And for good measure, it cleans them up again
on unmount. :)
The other threads are per-cpu workqueue threads that are shared
across all XFS filesystems in the system and hence are started
when XFS is initialised rather than when a mount occurs.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
|