public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] swiotlb: update format
Date: Mon, 2 Dec 2013 14:17:20 -0500	[thread overview]
Message-ID: <20131202191720.GB18624@phenom.dumpdata.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1311271347290.14638@pobox.suse.cz>

On Wed, Nov 27, 2013 at 01:48:09PM +0100, Jiri Kosina wrote:
> Documentation/kernel-parameters.txt doesn't contain up-to-date 
> documentation regarding swiotlb= parameter. Update it.

Thanks. Will queue it for 3.14
> 
> Signed-off-by: Jiri Kosina <jkosina@suse.cz>
> ---
>  Documentation/kernel-parameters.txt |    6 +++++-
>  1 files changed, 5 insertions(+), 1 deletions(-)
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index 50680a5..5577634 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -3061,7 +3061,11 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
>  			controller if no parameter or 1 is given or disable
>  			it if 0 is given (See Documentation/cgroups/memory.txt)
>  
> -	swiotlb=	[IA-64] Number of I/O TLB slabs
> +	swiotlb=	[ARM,IA-64,PPC,MIPS,X86]
> +			Format: { <int> | force }
> +			<int> -- Number of I/O TLB slabs
> +			force -- force using of bounce buffers even if they
> +			         wouldn't be automatically used by the kernel
>  
>  	switches=	[HW,M68k]
>  
> -- 
> Jiri Kosina
> SUSE Labs

      reply	other threads:[~2013-12-02 20:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-27 12:48 [PATCH] swiotlb: update format Jiri Kosina
2013-12-02 19:17 ` Konrad Rzeszutek Wilk [this message]

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=20131202191720.GB18624@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    /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