mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: "Xiaoming Wang" <xiaoming.wang@intel.com>
Cc: "Liu@aserp2030.oracle.com" <Liu@aserp2030.oracle.com>,
	"Zhang@aserp2030.oracle.com" <Zhang@aserp2030.oracle.com>,
	"chris@chris-wilson.co.uk" <chris@chris-wilson.co.uk>,
	"david.vrabel@citrix.com" <david.vrabel@citrix.com>,
	"lauraa@codeaurora.org" <lauraa@codeaurora.org>,
	"heiko.carstens@de.ibm.com" <heiko.carstens@de.ibm.com>,
	"linux@horizon.com" <linux@horizon.com>,
	"Chuansheng Liu" <chuansheng.liu@intel.com>,
	"Dongxing Zhang" <dongxing.zhang@intel.com>,
	"takahiro.akashi@linaro.org" <takahiro.akashi@linaro.org>,
	"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
	"linux-mips@linux-mips.org" <linux-mips@linux-mips.org>,
	"ralf@linux-mips.org" <ralf@linux-mips.org>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@oracle.com>,
	"d.kasatkin@samsung.com" <d.kasatkin@samsung.com>,
	"pebolle@tiscali.nl" <pebolle@tiscali.nl>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v5] modify the IO_TLB_SEGSIZE and IO_TLB_DEFAULT_SIZE configurable as flexible requirement about SW-IOMMU.
Date: Thu, 05 Mar 2015 08:40:11 +0000	[thread overview]
Message-ID: <54F8247B02000078000667AF@mail.emea.novell.com> (raw)
In-Reply-To: <FA47D36D6EC9FE4CB463299737C09B9901D05BBA@shsmsx102.ccr.corp.intel.com>

>>> On 05.03.15 at 04:53, <xiaoming.wang@intel.com> wrote:
>> From: Konrad Rzeszutek Wilk [mailto:konrad.wilk@oracle.com]
>> Sent: Thursday, March 5, 2015 3:43 AM
>> On Tue, Mar 03, 2015 at 04:11:09PM +0800, Wang Xiaoming wrote:
>> > @@ -101,13 +119,32 @@ setup_io_tlb_npages(char *str)  {
>> >  	if (isdigit(*str)) {
>> >  		io_tlb_nslabs = simple_strtoul(str, &str, 0);
>> > -		/* avoid tail segment of size < IO_TLB_SEGSIZE */
>> > -		io_tlb_nslabs = ALIGN(io_tlb_nslabs, IO_TLB_SEGSIZE);
>> >  	}
>> >  	if (*str == ',')
>> >  		++str;
>> > -	if (!strcmp(str, "force"))
>> > +	if (!strncmp(str, "force", 5)) {
>> >  		swiotlb_force = 1;
>> > +		str += 5;
>> > +	}
>> 
>> So the format is now:
>> 
>> 	Format: { <int> | force | <int> | <int>}
>> 
>> which means I can do
>> 	32,22323,force
>> 
>> Or
>> 	force,32
>> 
>> Or
>> 	32,force
>> 
> If I use Format: { <int>,force,<int>,<int>}
> 32,22323,force can't acceptable.
> There are three  <int>  here, if there are out of order, that will cause 
> confuse.
> Only 	32,force,32323
> Or	32,,32323,2322
> Or	,,323222,3232
> Are available.

You need to make sure that all previously valid variants are still
usable, i.e. force alone, a number alone, force,<number> and
<number>,force. How many variants you want to support with
your additions is mostly up to you; I'd recommend permitting force
in any position.

Jan


  reply	other threads:[~2015-03-05  8:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  8:11 Wang Xiaoming
2015-03-04 19:42 ` Konrad Rzeszutek Wilk
2015-03-05  3:53   ` Wang, Xiaoming
2015-03-05  8:40     ` Jan Beulich [this message]
2015-03-05  8:52       ` Wang, Xiaoming
2015-03-05  9:00         ` Jan Beulich
2015-03-06  1:12           ` Wang, Xiaoming
2015-03-06 15:19             ` Konrad Rzeszutek Wilk
2015-03-09  0:31               ` Wang, Xiaoming

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=54F8247B02000078000667AF@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=Liu@aserp2030.oracle.com \
    --cc=Zhang@aserp2030.oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=chuansheng.liu@intel.com \
    --cc=d.kasatkin@samsung.com \
    --cc=david.vrabel@citrix.com \
    --cc=dongxing.zhang@intel.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=konrad.wilk@oracle.com \
    --cc=lauraa@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@horizon.com \
    --cc=pebolle@tiscali.nl \
    --cc=ralf@linux-mips.org \
    --cc=takahiro.akashi@linaro.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xiaoming.wang@intel.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

Powered by JetHome