lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1157047058.31295.28.camel@localhost.localdomain>
Date:	Thu, 31 Aug 2006 10:57:38 -0700
From:	Dave Hansen <haveblue@...ibm.com>
To:	Christoph Lameter <clameter@....com>
Cc:	linux-mm@...ck.org, linux-kernel@...r.kernel.org,
	linux-ia64@...r.kernel.org
Subject: Re: [RFC][PATCH 3/9] actual generic PAGE_SIZE infrastructure

On Wed, 2006-08-30 at 17:08 -0700, Christoph Lameter wrote:
> On Wed, 30 Aug 2006, Dave Hansen wrote:
> 
> >  #endif	/* CONFIG_ARCH_HAVE_GET_ORDER */
> > -#endif /*  __ASSEMBLY__ */
> > +#endif  /* __ASSEMBLY__ */
>          ^^^ Extra blank.

OK.  I'll fix that.

> > +	prompt "Kernel Page Size"
> 	               page size?

Sure.

> > +	  This lets you select the page size of the kernel.  For best
> > +	  32-bit compatibility on 64-bit architectures, a page size of 4KB
> > +	  should be selected (although most binaries work perfectly fine with
> > +	  a larger page size).  For best performance, a page size of larger
> > +	  than 4KB is recommended.  However, there are a number of
> > +	  side-effects of larger page sizes, like small files fitting poorly
> > +	  into the page cache.
> 
> Could we change this somewhat? Avoid the direct address and maybe say:
> 
>  The kernel page size determines the basic chunk of memory handled
>  by the Linux VM. The bigger the page size the less page objects
>  have to be managed by the kernel which reduces the VM overhead in
>  handling large amounts of data. However, larger pages also lead
>  to memory being wasted by the kernel since small files will
>  at mininum require one page of memory. A 4K pagesize is fairly standard 
>  and may be required for 32 bit compatibility on many platforms.
> 
>  It is usually not wise to select another page size than the default
>  unless one knows what one is doing or has some time to spend on
>  getting to know the kernel.

This is very nice.  I'll incorporate it.  

> Note that the default pagesize on IA64 is 16K and some important things 
> would change if a lesser size is selected. I have never run a 4K kernel. 
> I do not think we can just say that 4KB is okay. There may be other 
> platforms that have other default page sizes.

If we can't just say that it is OK, then we should probably disable it
in Kconfig.  Should we do that?

-- Dave

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ