Re: [PATCH] mm: optimize PageHighMem() check

2015-11-06 Thread Vineet Gupta
On Saturday 03 October 2015 03:49 PM, Vineet Gupta wrote: > On Saturday 03 October 2015 02:23 AM, Andrew Morton wrote: >> > On Fri, 2 Oct 2015 12:45:53 +0530 Vineet Gupta wrote: >> > >>> >> On Friday 02 October 2015 04:55 AM, Andrew Morton wrote: >>> On Tue, 29 Sep 2015 13:24:20 +0530 Vineet

Re: [PATCH] mm: optimize PageHighMem() check

2015-10-03 Thread Vineet Gupta
On Saturday 03 October 2015 02:23 AM, Andrew Morton wrote: > On Fri, 2 Oct 2015 12:45:53 +0530 Vineet Gupta wrote: > >> On Friday 02 October 2015 04:55 AM, Andrew Morton wrote: >>> On Tue, 29 Sep 2015 13:24:20 +0530 Vineet Gupta >>> wrote: >>> > This came up when implementing HIHGMEM/PAE40 f

Re: [PATCH] mm: optimize PageHighMem() check

2015-10-02 Thread Andrew Morton
On Fri, 2 Oct 2015 12:45:53 +0530 Vineet Gupta wrote: > On Friday 02 October 2015 04:55 AM, Andrew Morton wrote: > > On Tue, 29 Sep 2015 13:24:20 +0530 Vineet Gupta > > wrote: > > > >> > This came up when implementing HIHGMEM/PAE40 for ARC. > >> > The kmap() / kmap_atomic() generated code seem

Re: [PATCH] mm: optimize PageHighMem() check

2015-10-02 Thread Vineet Gupta
On Friday 02 October 2015 04:55 AM, Andrew Morton wrote: > On Tue, 29 Sep 2015 13:24:20 +0530 Vineet Gupta > wrote: > >> > This came up when implementing HIHGMEM/PAE40 for ARC. >> > The kmap() / kmap_atomic() generated code seemed needlessly bloated due >> > to the way PageHighMem() macro is imp

Re: [PATCH] mm: optimize PageHighMem() check

2015-10-01 Thread Andrew Morton
On Tue, 29 Sep 2015 13:24:20 +0530 Vineet Gupta wrote: > This came up when implementing HIHGMEM/PAE40 for ARC. > The kmap() / kmap_atomic() generated code seemed needlessly bloated due > to the way PageHighMem() macro is implemented. > It derives the exact zone for page and then does pointer sub

Re: [PATCH] mm: optimize PageHighMem() check

2015-10-01 Thread Michal Hocko
On Tue 29-09-15 13:24:20, Vineet Gupta wrote: > This came up when implementing HIHGMEM/PAE40 for ARC. > The kmap() / kmap_atomic() generated code seemed needlessly bloated due > to the way PageHighMem() macro is implemented. > It derives the exact zone for page and then does pointer subtraction > w