[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9A15F5E5-775E-4079-961F-67FD54B8F2F4@oracle.com>
Date: Thu, 23 Jun 2016 12:06:10 -0400
From: Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
To: Catalin Marinas <catalin.marinas@....com>,
Manjeet Pawar <manjeet.p@...sung.com>
CC: corbet@....net, will.deacon@....com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
r.thapliyal@...sung.com, akhilesh.k@...sung.com,
ajeet.y@...sung.com, pankaj.m@...sung.com
Subject: Re: [PATCH] arm64:swiotlb:Enable only when Input size through command line
On June 23, 2016 10:30:34 AM EDT, Catalin Marinas <catalin.marinas@....com> wrote:
>On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
>> From: Rohit Thapliyal <r.thapliyal@...sung.com>
>>
>> swiotlb default size of 64M is too big as
>> default value therefore it is made configurable
>> through command line through swiotlb_size parameter.
>> swiotlb allocation shall be done only when the
>> swiotlb size is given through command line.
>> Otherwise no swiotlb is allocated.
>
>I already queued this patch:
>
>http://lkml.kernel.org/g/1465372426-4077-1-git-send-email-jszhang@marvell.com
>
>If you have any objections to it, please reply there.
I do (sorry about duplicate email, the other got rejected by mailing lists).
Why not expand the swiotlb= parameter instead of introducing a new one?
Also, why not use the swiotlb by itself? That does the job as well?
Powered by blists - more mailing lists