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] [day] [month] [year] [list]
Message-ID: <20091013144504.GC8175@mit.edu>
Date:	Tue, 13 Oct 2009 10:45:04 -0400
From:	Theodore Tso <tytso@....edu>
To:	飞颜 <win847@...il.com>
Cc:	Tim Abbott <tabbott@...lice.com>, Greg Ungerer <gerg@...pgear.com>,
	linux-kernel@...r.kernel.org, Sam Ravnborg <sam@...nborg.org>
Subject: Re: Drivers compiled into the kernel can reduce code size

On Tue, Oct 13, 2009 at 01:46:18PM +0800, 飞颜 wrote:
> Dear all,
> 
>        I has a question below:
> 
>      Why Drivers compiled into the kernel can reduce code size
> compared with Module ways?
> 
>      Kernel + Driver Module (Code Size) > Kernel(include Driver)

Each loadable kernel module is subject to rounding to 4k pages, where
as when a driver is built into the kernel, its text, data, and BSS
segments can be included into the kernel text, data, and BSS segments. 

Drivers that are compiled into the kernel also can use the same single
huge page TLB entry for the kernel text segment, so using a fewer
kernel modules can also result in fewer TLB misses.

       	       	   	       	  	    - Ted
--
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