Kirill A. Shutemov with the commit 96bacfe542 introduced
vm_ops->map_pages() for mapping easy accessible pages around
fault address in hope to reduce number of minor page faults.
Based on his workload runs, suggested FAULT_AROUND_ORDER
(knob to control the numbers of pages to map) is 4.
This patch
Performance data for different FAULT_AROUND_ORDER values from 4 socket
Power7 system (128 Threads and 128GB memory) is below. Fault around order (FAO)
value of 3 looks more advantageous.
FAULT_AROUND_ORDER Baseline1 3 4
5 7
Li
Hi Vasant,
> On 02/09/2014 02:50 AM, Anton Blanchard wrote:
> >
> > Hi Vasant,
> >
> >> +static void free_dump_sg_list(struct opal_sg_list *list)
> >> +{
> >> + struct opal_sg_list *sg1;
> >> + while (list) {
> >> + sg1 = list->next;
> >> + kfree(list);
> >> + list = s
On 03/25/2014 10:17 AM, 许久成 wrote:
Hi All,
We run into an issue when use e500mc toolchain g++ to compile c++
code for p2020 platform, the code as below:
Hmm, p2020 should be e500 core rather than e500mc. Additionally, you
should use gdb to debug it, and check which instruction is illegal.
Hi, Sandeep Gopalpet
I am a developer. Now I confronted an interesting phenomena. When I used
linux kernel 2.6.34.15 on freescale-p2020, I can not receive raw and
vlan packets on gfar-enet nic. But with e1000e nic, we can make vlan and
raw packets work well. I looked into the source code and f
Hi All,
We run into an issue when use e500mc toolchain g++ to compile c++ code for
p2020 platform, the code as below:
main.c
#include using namespace std;
int main(void) {cout << "asdfasdfasdfasdf";
return 0;}
compile it with command "powerpc-fls-linux-g++ main.c" and the output
This is a defconfig. You need to run "make mpc85xx_defconfig" to get the
.config file which is used to compile kernel.
Regards,
Mingkai
-Original Message-
From: Michael Neuling [mailto:mi...@neuling.org]
Sent: Tuesday, March 25, 2014 9:16 AM
To: Kumar Gala; Wood Scott-B07421; b...@kernel
Scott,
> On Tue, 2014-03-25 at 12:15 +1100, Michael Neuling wrote:
> > These are always breaking and I feel like I'm the only one fixing them
> > and
>
> Always? Please elaborate.
Maybe once every 2-3 months I have to send a fix up for them.
> > I don't even have one of these boards so let's
On Tue, 2014-03-25 at 12:15 +1100, Michael Neuling wrote:
> These are always breaking and I feel like I'm the only one fixing them
> and
Always? Please elaborate.
> I don't even have one of these boards so let's just remove them.
What does you having one of these boards have to do with anythin
These are always breaking and I feel like I'm the only one fixing them
and I don't even have one of these boards so let's just remove them.
They are also broken right now in linux-next when compiling modules.
Signed-off-by: Michael Neuling
diff --git a/arch/powerpc/configs/mpc85xx_defconfig
b/
On Mon, 2014-03-24 at 10:33 +1100, Benjamin Herrenschmidt wrote:
> On Mon, 2014-03-24 at 10:16 +1100, Benjamin Herrenschmidt wrote:
> > On Wed, 2014-03-19 at 23:25 -0500, Scott Wood wrote:
> > > The following changes since commit
> > > c7e64b9ce04aa2e3fad7396d92b5cb92056d16ac:
> > >
> > > power
next-20140324 currently fails compiling celleb_defconfig with:
arch/powerpc/include/asm/opal.h:894:42: error: 'struct notifier_block' declared
inside parameter list [-Werror]
arch/powerpc/include/asm/opal.h:894:42: error: its scope is only this
definition or declaration, which is pr
Anyone have any ideas here?
On 13.03.2014 [10:01:27 -0700], Nishanth Aravamudan wrote:
> There might have been an error in my original mail, so resending...
>
> On 11.03.2014 [14:06:14 -0700], Nishanth Aravamudan wrote:
> > We have seen the following situation on a test system:
> >
> > 2-node sy
In KVM guests on Power, if the guest is not backed by hugepages, we see
the following in the guest:
AnonHugePages: 0 kB
HugePages_Total: 0
HugePages_Free:0
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize: 64 kB
This seems like a configuration issue --
On Tue, Mar 18, 2014 at 04:10:24PM -0500, Scott Wood wrote:
> Fixes a build break due to the undeclared use of irq_of_parse_and_map()
> and of_iomap(). This build break was apparently introduced while the
> driver was unbuildable due to the bug fixed by
> 62c19c9d29e65086e5ae76df371ed2e6b23f00cd (
Patch 15/18 "powerpc/boot: add a global entry point for pseries"
introduced a pseries-head.S file to fix the endian order when
entering the boot wrapper. This patch is a fix for some platforms
which also generate the zImage.pseries boot wrapper.
Signed-off-by: Cédric Le Goater
---
Ben,
You can p
On Sat, Mar 22, 2014 at 03:59:11PM -0700, James Bottomley wrote:
> On Sat, 2014-03-22 at 22:52 +, Russell King - ARM Linux wrote:
> > And I'm disagreeing with that statement which implies that it's something
> > that is an architecture wide property for any particular architecture.
> >
> > Rig
On Mon, 2014-03-24 at 09:38 +0100, Cedric Le Goater wrote:
> Hi Benjamin,
>
> > So I originally applied all 3 last patches of the series as one
> > (collapsed them in git) in order to not break bisection.
> >
> > However, I had to take the series out in the end due to it
> > causing this error on
Hi Benjamin,
> So I originally applied all 3 last patches of the series as one
> (collapsed them in git) in order to not break bisection.
>
> However, I had to take the series out in the end due to it
> causing this error on some of my test configs:
>
> powerpc64-linux-ld: cannot find arch/power
19 matches
Mail list logo
