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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 9 Nov 2009 10:11:28 +0000
From:	Mel Gorman <>
To:	Pavel Machek <>
Cc:	David Rientjes <>,
	Christoph Lameter <>,
	Rik van Riel <>,
	Andrew Morton <>,,,,
	Frans Pop <>, Jiri Kosina <>,
	Sven Geggus <>,
	Karol Lewandowski <>,
	Tobias Oetiker <>,
	KOSAKI Motohiro <>,
	Pekka Enberg <>,
	Stephan von Krawczynski <>,
Subject: Re: [PATCH 2/3] page allocator: Do not allow interrupts to use

On Wed, Nov 04, 2009 at 10:01:40AM +0100, Pavel Machek wrote:
> > I hope we can move this to another thread if people would like to remove 
> > this exemption completely instead of talking about this trivial fix, which 
> > I doubt there's any objection to.
> I'm arguing that this "trivial fix" is wrong, and that you should just
> remove those two lines.
> If going into reserves from interrupts hurts, doing that from task
> context will hurt, too. "realtime" task should not be normally allowed
> to "hurt" the system like that.
> 									Pavel

As David points out, it has been the behaviour of the system for 4 years
and removing it should be made as a separate decision and not in the
guise of a fix. In the particular case causing concern, there are a lot
more allocations from interrupt due to network receive than there are
from the activities of tasks with a high priority.

Mel Gorman
Part-time Phd Student                          Linux Technology Center
University of Limerick                         IBM Dublin Software Lab
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