Hi,
On 12/03/14 at 11:35am, Joerg Roedel wrote:
> Hi,
>
> On Wed, Dec 03, 2014 at 12:01:23PM +0800, WANG Chao wrote:
> >From your experience It seems like swiotlb isn't working well with
> > crashkernel=X,high alone. What about using crashkernel=X,low with
> > crashkernel=X,high? Is there any rea
Hi,
On Wed, Dec 03, 2014 at 12:01:23PM +0800, WANG Chao wrote:
>From your experience It seems like swiotlb isn't working well with
> crashkernel=X,high alone. What about using crashkernel=X,low with
> crashkernel=X,high? Is there any reason you have to use
> crashkernel=X,high alone?
Sure, when I
> Hi,
>
> here is a patch-set to fix failed kdump kernel boots when
> the systems was booted with crashkernel=X,high. On those
> systems the kernel allocates only 72MiB of low-memory for
> DMA buffers, which showed to be too low on some systems.
>From your experience It seems like swiotlb isn't w
On Tue, Dec 02, 2014 at 07:30:09PM +0800, Baoquan He wrote:
> The default low memory is calculated in swiotlb_size_or_default(), and
> this relies on IO_TLB_DEFAULT_SIZE which is default value for swiotlb.
> If this doesn't work for your case in kdump kernel, does the default
> value IO_TLB_DEFAULT
On 11/28/2014 07:29 PM, Joerg Roedel wrote:
> Hi,
>
> here is a patch-set to fix failed kdump kernel boots when
> the systems was booted with crashkernel=X,high. On those
> systems the kernel allocates only 72MiB of low-memory for
> DMA buffers, which showed to be too low on some systems.
>
> The
Hi,
here is a patch-set to fix failed kdump kernel boots when
the systems was booted with crashkernel=X,high. On those
systems the kernel allocates only 72MiB of low-memory for
DMA buffers, which showed to be too low on some systems.
The problem is that 64MiB of the low-memory is allocated by
swi
6 matches
Mail list logo