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  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]
Date:	Mon, 28 Jul 2014 15:43:26 -0700 (PDT)
From:	David Rientjes <>
To:	Andrey Ryabinin <>
cc:	"Kirill A. Shutemov" <>,
	Sasha Levin <>,
	Andrew Morton <>,
	Linus Torvalds <>,
	Andi Kleen <>,
	Matthew Wilcox <>,
	Dave Hansen <>,
	Alexander Viro <>,
	Dave Chinner <>, Ning Qu <>,,,, Dave Jones <>,,
	"Kirill A. Shutemov" <>,
	Mel Gorman <>, Rik van Riel <>,
	Konstantin Khlebnikov <>,
	Hugh Dickins <>
Subject: Re: [PATCH] mm: don't allow fault_around_bytes to be 0

On Mon, 28 Jul 2014, Andrey Ryabinin wrote:

> do_fault_around expects fault_around_bytes rounded down to nearest
> page order. Instead of calling rounddown_pow_of_two every time
> in fault_around_pages()/fault_around_mask() we could do round down
> when user changes fault_around_bytes via debugfs interface.

If you're going to optimize this, it seems like fault_around_bytes would 
benefit from being __read_mostly.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists