HATAYAMA Daisuke writes:
> The breakage was caused by the introduction of new NT_VMCORE_PAD to
> "VMCOREINFO" name, except for which it worked fine. But it will be
> dropped in the next version. It'll be no problem for some time.
>
> The breakage was caused by makedumpfile itself due to the bug
From: "Eric W. Biederman"
Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
Date: Wed, 20 Mar 2013 23:16:20 -0700
> HATAYAMA Daisuke writes:
>
>> From: Andrew Morton
>> Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc
HATAYAMA Daisuke writes:
> From: Andrew Morton
> Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
> Date: Tue, 19 Mar 2013 12:30:05 -0700
>
>> On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke
>> wrote:
>>
>>>
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com writes:
From: Andrew Morton a...@linux-foundation.org
Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
Date: Tue, 19 Mar 2013 12:30:05 -0700
On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke
d.hatay...@jp.fujitsu.com
From: Eric W. Biederman ebied...@xmission.com
Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
Date: Wed, 20 Mar 2013 23:16:20 -0700
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com writes:
From: Andrew Morton a...@linux-foundation.org
Subject: Re: [PATCH v3 00/21] kdump
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com writes:
The breakage was caused by the introduction of new NT_VMCORE_PAD to
VMCOREINFO name, except for which it worked fine. But it will be
dropped in the next version. It'll be no problem for some time.
The breakage was caused by makedumpfile
From: Andrew Morton
Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
Date: Tue, 19 Mar 2013 12:30:05 -0700
> On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke
> wrote:
>
>> Currently, read to /proc/vmcore is done by read_oldmem() that uses
>>
From: Andrew Morton a...@linux-foundation.org
Subject: Re: [PATCH v3 00/21] kdump, vmcore: support mmap() on /proc/vmcore
Date: Tue, 19 Mar 2013 12:30:05 -0700
On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke
d.hatay...@jp.fujitsu.com wrote:
Currently, read to /proc/vmcore is done
HATAYAMA Daisuke writes:
> Currently, read to /proc/vmcore is done by read_oldmem() that uses
> ioremap/iounmap per a single page. For example, if memory is 1GB,
> ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
> times. This causes big performance degradation.
>
> In particular,
On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke
wrote:
> Currently, read to /proc/vmcore is done by read_oldmem() that uses
> ioremap/iounmap per a single page. For example, if memory is 1GB,
> ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
> times. This causes big performance
On Sat, 16 Mar 2013 13:00:47 +0900 HATAYAMA Daisuke d.hatay...@jp.fujitsu.com
wrote:
Currently, read to /proc/vmcore is done by read_oldmem() that uses
ioremap/iounmap per a single page. For example, if memory is 1GB,
ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
times. This
HATAYAMA Daisuke d.hatay...@jp.fujitsu.com writes:
Currently, read to /proc/vmcore is done by read_oldmem() that uses
ioremap/iounmap per a single page. For example, if memory is 1GB,
ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
times. This causes big performance degradation.
Currently, read to /proc/vmcore is done by read_oldmem() that uses
ioremap/iounmap per a single page. For example, if memory is 1GB,
ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
times. This causes big performance degradation.
In particular, the current main user of this mmap() is
Currently, read to /proc/vmcore is done by read_oldmem() that uses
ioremap/iounmap per a single page. For example, if memory is 1GB,
ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144
times. This causes big performance degradation.
In particular, the current main user of this mmap() is
14 matches
Mail list logo
