From: Ben Hutchings <bhutchings@solarflare.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-net-drivers@solarflare.com>,
Stuart Hodgson <smhodgson@solarflare.com>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
<linux-s390@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: Build regressions/improvements in v3.10-rc1 (s390)
Date: Mon, 13 May 2013 17:41:47 +0100 [thread overview]
Message-ID: <1368463307.3305.23.camel@bwh-desktop.uk.solarflarecom.com> (raw)
In-Reply-To: <20130513074159.GA4290@osiris>
On Mon, 2013-05-13 at 09:41 +0200, Heiko Carstens wrote:
> On Sun, May 12, 2013 at 10:50:45PM +0200, Geert Uytterhoeven wrote:
> > On Sun, 12 May 2013, Geert Uytterhoeven wrote:
> > > However, the full list of errors isn't that unmanageable, so I'm following
> > > up with a digested list...
> >
> > drivers/net/ethernet/sfc/efx.c:646:3: error: call to '__compiletime_assert_648' declared with attribute error: BUILD_BUG_ON failed: sizeof(struct efx_rx_page_state) + EFX_PAGE_IP_ALIGN + EFX_RX_USR_BUF_SIZE > PAGE_SIZE / 2: 2 errors in 2 logs
> > v3.10-rc1/s390x/s390-allyesconfig v3.10-rc1/s390x/s390-allmodconfig
>
> that seems to a BUILD_BUG_ON that only triggers on s390, because we have
> L1_CACHE_BYTES defined with 256 bytes... which seems to be more than any
> other architecture has.
> There was a different network driver that had a similar BUILD_BUG_ON, but
> it got removed.
>
> Right, it was the igb driver:
> http://comments.gmane.org/gmane.linux.network/261378
The critical value here is EFX_RX_USR_BUF_SIZE. The hardware constrains
it to be a multiple of 32, but for performance reasons it also ought to
be a multiple of the cache line size(s). In our internal development
branch it has already been reduced to 1792, which is a multiple of 256
and should satisfy the BUILD_BUG_ON check. I'll post a patch shortly.
Ben.
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2013-05-13 16:41 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-12 19:30 Build regressions/improvements in v3.10-rc1 Geert Uytterhoeven
2013-05-12 20:41 ` Geert Uytterhoeven
2013-05-12 20:42 ` Build regressions/improvements in v3.10-rc1 (sh) Geert Uytterhoeven
2013-05-12 20:44 ` Build regressions/improvements in v3.10-rc1 (cris) Geert Uytterhoeven
2013-05-14 12:06 ` Geert Uytterhoeven
2013-05-14 16:33 ` Jesper Nilsson
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (avr) Geert Uytterhoeven
2013-05-13 12:54 ` Hans-Christian Egtvedt
2013-05-13 13:00 ` Geert Uytterhoeven
2013-05-12 20:45 ` Build regressions/improvements in v3.10-rc1 (h8300) Geert Uytterhoeven
2013-05-12 20:46 ` Build regressions/improvements in v3.10-rc1 (mips) Geert Uytterhoeven
2013-06-11 13:37 ` Markos Chandras
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (powerpc) Geert Uytterhoeven
2013-05-12 20:47 ` Build regressions/improvements in v3.10-rc1 (um) Geert Uytterhoeven
2013-05-12 21:17 ` richard -rw- weinberger
2013-05-13 8:18 ` Geert Uytterhoeven
2013-05-13 9:54 ` Michael Ellerman
2013-05-13 10:02 ` Geert Uytterhoeven
2013-05-13 10:07 ` richard -rw- weinberger
2013-05-13 10:18 ` Geert Uytterhoeven
2013-05-13 10:20 ` richard -rw- weinberger
2013-05-15 2:48 ` Stephen Rothwell
2013-05-13 12:15 ` Michael Ellerman
2013-05-15 2:57 ` Stephen Rothwell
2013-05-15 6:50 ` Geert Uytterhoeven
2013-05-12 20:49 ` Build regressions/improvements in v3.10-rc1 (crypto/parisc) Geert Uytterhoeven
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (staging) Geert Uytterhoeven
2013-05-12 21:43 ` Greg KH
2013-05-12 20:50 ` Build regressions/improvements in v3.10-rc1 (s390) Geert Uytterhoeven
2013-05-13 7:41 ` Heiko Carstens
2013-05-13 16:41 ` Ben Hutchings [this message]
2013-05-12 22:13 ` Build regressions/improvements in v3.10-rc1 Randy Dunlap
2013-05-13 8:37 ` Geert Uytterhoeven
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=1368463307.3305.23.camel@bwh-desktop.uk.solarflarecom.com \
--to=bhutchings@solarflare.com \
--cc=geert@linux-m68k.org \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net-drivers@solarflare.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=smhodgson@solarflare.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
all inboxes | Powered by JetHome®