On Mon, Nov 05, 2018 at 07:59:13AM +0300, Vasily Averin wrote:
>
>
> On 11/5/18 3:50 AM, Huang, Ying wrote:
> > Vasily Averin writes:
> >
> >> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> >> increased size of swap_info_struct up to 44 Kbytes, now it requires
> >>
On Mon, Nov 05, 2018 at 07:59:13AM +0300, Vasily Averin wrote:
>
>
> On 11/5/18 3:50 AM, Huang, Ying wrote:
> > Vasily Averin writes:
> >
> >> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> >> increased size of swap_info_struct up to 44 Kbytes, now it requires
> >>
Vasily Averin writes:
> On 11/5/18 3:50 AM, Huang, Ying wrote:
>> Vasily Averin writes:
>>
>>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>>> 4th order page.
>>
>> Why swap_info_struct could
Vasily Averin writes:
> On 11/5/18 3:50 AM, Huang, Ying wrote:
>> Vasily Averin writes:
>>
>>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>>> 4th order page.
>>
>> Why swap_info_struct could
On 11/5/18 3:50 AM, Huang, Ying wrote:
> Vasily Averin writes:
>
>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>> 4th order page.
>
> Why swap_info_struct could be so large? Because
On 11/5/18 3:50 AM, Huang, Ying wrote:
> Vasily Averin writes:
>
>> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
>> increased size of swap_info_struct up to 44 Kbytes, now it requires
>> 4th order page.
>
> Why swap_info_struct could be so large? Because
Vasily Averin writes:
> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> increased size of swap_info_struct up to 44 Kbytes, now it requires
> 4th order page.
Why swap_info_struct could be so large? Because MAX_NUMNODES could be
thousands so that 'avail_lists' field
Vasily Averin writes:
> commit a2468cc9bfdf ("swap: choose swap device according to numa node")
> increased size of swap_info_struct up to 44 Kbytes, now it requires
> 4th order page.
Why swap_info_struct could be so large? Because MAX_NUMNODES could be
thousands so that 'avail_lists' field
commit a2468cc9bfdf ("swap: choose swap device according to numa node")
increased size of swap_info_struct up to 44 Kbytes, now it requires 4th order
page.
Switch to kvzmalloc allows to avoid unexpected allocation failures.
Signed-off-by: Vasily Averin
---
mm/swapfile.c | 6 +++---
1 file
commit a2468cc9bfdf ("swap: choose swap device according to numa node")
increased size of swap_info_struct up to 44 Kbytes, now it requires 4th order
page.
Switch to kvzmalloc allows to avoid unexpected allocation failures.
Signed-off-by: Vasily Averin
---
mm/swapfile.c | 6 +++---
1 file
10 matches
Mail list logo