[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20111008.155158.566839176815794249.davem@davemloft.net>
Date: Sat, 08 Oct 2011 15:51:58 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: jeffrey.t.kirsher@...el.com
Cc: alexander.h.duyck@...el.com, netdev@...r.kernel.org,
gospo@...hat.com, sassmann@...hat.com
Subject: Re: [net-next 02/11] igb: Use node specific allocations for the
q_vectors and rings
From: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
Date: Fri, 7 Oct 2011 23:47:32 -0700
> From: Alexander Duyck <alexander.h.duyck@...el.com>
>
> This change is meant to update the ring and vector allocations so that they
> are per node instead of allocating everything on the node that
> ifconfig/modprobe is called on. By doing this we can cut down
> significantly on cross node traffic.
>
> Signed-off-by: Alexander Duyck <alexander.h.duyck@...el.com>
> Tested-by: Aaron Brown <aaron.f.brown@...el.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
adapter->node seems superfluous.
It's always "-1" when we enter the allocation functions, and we
always restore it to it's original value upon exit from such
functions.
Just get rid of it and use a local variable in these functions
to keep track of the current allocation node.
Also, what ensures that MSI-X interrupts are targetted to a cpu
on the the node where you've made these allocations? I was
pretty sure Ben Hutchings added infrastructure that's usable
to ensure this, but I can't see where you're using it.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists