From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Manjeet Pawar <manjeet.p@samsung.com>
Cc: corbet@lwn.net, will.deacon@arm.com, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, r.thapliyal@samsung.com,
akhilesh.k@samsung.com, ajeet.y@samsung.com,
pankaj.m@samsung.com
Subject: Re: [PATCH] arm64:swiotlb:Enable only when Input size through command line
Date: Thu, 23 Jun 2016 12:06:10 -0400 [thread overview]
Message-ID: <9A15F5E5-775E-4079-961F-67FD54B8F2F4@oracle.com> (raw)
In-Reply-To: <20160623143034.GN6521@e104818-lin.cambridge.arm.com>
On June 23, 2016 10:30:34 AM EDT, Catalin Marinas <catalin.marinas@arm.com> wrote:
>On Thu, Jun 23, 2016 at 05:43:40PM +0530, Manjeet Pawar wrote:
>> From: Rohit Thapliyal <r.thapliyal@samsung.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?
next prev parent reply other threads:[~2016-06-23 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-23 12:13 [PATCH] arm64:swiotlb:Enable only when Input size through command line Manjeet Pawar
2016-06-23 12:31 ` Robin Murphy
2016-06-23 14:30 ` Catalin Marinas
2016-06-23 16:06 ` Konrad Rzeszutek Wilk [this message]
2016-06-24 2:57 ` Jisheng Zhang
2016-06-24 10:46 ` Konrad Rzeszutek Wilk
2016-06-24 10:53 ` Robin Murphy
2016-06-23 14:38 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9A15F5E5-775E-4079-961F-67FD54B8F2F4@oracle.com \
--to=konrad.wilk@oracle.com \
--cc=ajeet.y@samsung.com \
--cc=akhilesh.k@samsung.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manjeet.p@samsung.com \
--cc=pankaj.m@samsung.com \
--cc=r.thapliyal@samsung.com \
--cc=will.deacon@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).