linux-kernel - Re: [RFC PATCH v1 2/3] PM / Runtime: force memory allocation with no I/O during runtime

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: <CACVXFVP-JerxiTU9Kr9Lrwe2XkKBU=EsZJUcEiPVCQWw6iiw2Q@mail.gmail.com>
Date:	Wed, 17 Oct 2012 19:07:25 +0800
From:	Ming Lei <ming.lei@...onical.com>
To:	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	linux-kernel@...r.kernel.org,
	Alan Stern <stern@...land.harvard.edu>,
	Oliver Neukum <oneukum@...e.de>,
	Minchan Kim <minchan@...nel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	linux-usb@...r.kernel.org, linux-pm@...r.kernel.org
Subject: Re: [RFC PATCH v1 2/3] PM / Runtime: force memory allocation with no
 I/O during runtime_resume callbcack

On Wed, Oct 17, 2012 at 1:43 PM, Rafael J. Wysocki <rjw@...k.pl> wrote:
>
> This appears to be a bit too heavy handed.  First of all, it seems to affect
> all memory allocations going in parallel with the resume callback.  Second,

No, the flag is per task, only memory allocation inside resume callback
is effected.

> it affects all resume callbacks, not only those where the problem really

We can do it only on block device, block device's ancestor and network
devices(iSCSI case), but that may introduce policy into PM core or add
one flag of memalloc_noio_resume into 'dev_pm_info', could you agree
on it?


Thanks,
--
Ming Lei
--
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/