On Fri, Jan 18, 2013 at 5:57 AM, Andrew Morton
wrote:
>
> Fair enough, thanks.
>
> I grabbed the patches for 3.9-rc1. It is good that the page
> allocator's newly-added test of current->flags is not on the fastpath.
>
Andrew, great thanks, :-)
Also thank Alan, Oliver, Minchan, Rafael, Greg and
On Thu, 17 Jan 2013 09:28:14 +0800
Ming Lei wrote:
> > If so, I wonder if we could avoid the whole problem by appropriately
> > syncing all dirty memory back to storage before starting to turn devices
> > off?
>
> The patchset is to address the probable deadlock problem by GFP_KERNEL
> during ru
On Thursday 17 January 2013 09:28:14 Ming Lei wrote:
> - we still need some synchronization to avoid accessing the storage
>between sys_sync and device suspend, just like system sleep case,
>pm_restrict_gfp_mask is needed even sys_sync has been done
>inside enter_state(
On Thu, Jan 17, 2013 at 7:37 AM, Andrew Morton
wrote:
> On Sat, 5 Jan 2013 10:25:38 +0800
> Ming Lei wrote:
>
>> This patchset try to solve one deadlock problem which might be caused
>> by memory allocation with block I/O during runtime PM and block device
>> error handling path. Traditionly, th
On Sat, 5 Jan 2013 10:25:38 +0800
Ming Lei wrote:
> This patchset try to solve one deadlock problem which might be caused
> by memory allocation with block I/O during runtime PM and block device
> error handling path. Traditionly, the problem is addressed by passing
> GFP_NOIO statically to mm,
Hi,
This patchset try to solve one deadlock problem which might be caused
by memory allocation with block I/O during runtime PM and block device
error handling path. Traditionly, the problem is addressed by passing
GFP_NOIO statically to mm, but that is not a effective solution, see
detailed descr
6 matches
Mail list logo
