public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jiang, Dave" <dave.jiang@intel.com>
To: "Williams, Dan J" <dan.j.williams@intel.com>,
	"tim.gardner@canonical.com" <tim.gardner@canonical.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"der.herr@hofr.at" <der.herr@hofr.at>,
	"Koul, Vinod" <vinod.koul@intel.com>,
	"prarit@redhat.com" <prarit@redhat.com>,
	"jarkko.nikula@linux.intel.com" <jarkko.nikula@linux.intel.com>
Subject: Re: [PATCH v4.4-rc8 v3] dmaengine: ioatdma: Squelch framesize warnings
Date: Fri, 8 Jan 2016 19:58:47 +0000	[thread overview]
Message-ID: <1452283126.3983.41.camel@intel.com> (raw)
In-Reply-To: <CAPcyv4g_SeB2LDuv7=KEWithUwe_HgbUb5XzmnDuE+1DESAf4Q@mail.gmail.com>

On Fri, 2016-01-08 at 19:41 +0000, Williams, Dan J wrote:
> On Fri, Jan 8, 2016 at 11:25 AM,  <tim.gardner@canonical.com> wrote:
> > From: Tim Gardner <tim.gardner@canonical.com>
> > 
> >   CC [M]  drivers/dma/ioat/prep.o
> > drivers/dma/ioat/prep.c: In function 'ioat_prep_pqxor':
> > drivers/dma/ioat/prep.c:682:1: warning: the frame size of 1048
> > bytes is larger than 1024 bytes [-Wframe-larger-than=]
> >  }
> >  ^
> > drivers/dma/ioat/prep.c: In function 'ioat_prep_pqxor_val':
> > drivers/dma/ioat/prep.c:714:1: warning: the frame size of 1048
> > bytes is larger than 1024 bytes [-Wframe-larger-than=]
> >  }
> > 
> > gcc version 5.3.1 20151219 (Ubuntu 5.3.1-4ubuntu1)
> > 
> > Cc: Vinod Koul <vinod.koul@intel.com>
> > Cc: Dan Williams <dan.j.williams@intel.com>
> > Cc: Dave Jiang <dave.jiang@intel.com>
> > Cc: Prarit Bhargava <prarit@redhat.com>
> > Cc: Nicholas Mc Guire <der.herr@hofr.at>
> > Cc: Jarkko Nikula <jarkko.nikula@linux.intel.com>
> > Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> > ---
> > 
> > v2 - use per CPU static buffers instead of dynamically allocating
> > memory.
> > v3 - Use get_cpu_var/put_cpu_var which implicitly control
> > preeemption. Drop
> >      the wrapper function that no longer serves any purpose.
> > 
> >  drivers/dma/ioat/prep.c | 29 +++++++++++++++++++++++++----
> >  1 file changed, 25 insertions(+), 4 deletions(-)
> 
> Looks good to me... but now that I think about it, why is MAX_SCF set
> to 1024 in the first place?  Certainly it can't be bigger than the
> maximum number of sources in a single operation which is 8 to 16.
> Even md raid can only support up to 256 devices in an array.  So I
> think that contstant is bogus.
> 
> If we set it to 16 we may not even need the percpu change.
> 
> Dave?

You are right. It was an arbitrary number I threw in there to address
sparse warning. It can be reduced. 256 seems reasonable. 

  reply	other threads:[~2016-01-08 19:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 18:07 [PATCH v4.4-rc8] dmaengine: ioatdma: Squelch framesize warnings tim.gardner
2016-01-07 19:45 ` Dan Williams
2016-01-08 13:35 ` [PATCH v4.4-rc8 v2] " tim.gardner
2016-01-08 16:39   ` Dan Williams
2016-01-08 19:25     ` [PATCH v4.4-rc8 v3] " tim.gardner
2016-01-08 19:41       ` Dan Williams
2016-01-08 19:58         ` Jiang, Dave [this message]
2016-01-08 21:48           ` [PATCH v4.4-rc8 v4] " tim.gardner
2016-01-13 13:28             ` Vinod Koul

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=1452283126.3983.41.camel@intel.com \
    --to=dave.jiang@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=der.herr@hofr.at \
    --cc=dmaengine@vger.kernel.org \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=prarit@redhat.com \
    --cc=tim.gardner@canonical.com \
    --cc=vinod.koul@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