From: Eric Dumazet <eric.dumazet@gmail.com>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, Vasu Dev <vasu.dev@intel.com>,
netdev@vger.kernel.org, gospo@redhat.com
Subject: Re: [net-next 13/13] ixgbe: use per NUMA node lock for FCoE DDP
Date: Sat, 11 Jun 2011 07:18:02 +0200 [thread overview]
Message-ID: <1307769482.2872.62.camel@edumazet-laptop> (raw)
In-Reply-To: <1307761341-5267-14-git-send-email-jeffrey.t.kirsher@intel.com>
Le vendredi 10 juin 2011 à 20:02 -0700, Jeff Kirsher a écrit :
> From: Vasu Dev <vasu.dev@intel.com>
>
> Adds per NUMA node lock to have CPU pass thru its NUMA lock
> first before contending for global DDP fcoe->lock to setup
> DDP lock, this is to reduce contentions across NUMA nodes.
>
> Allocates and initialize per NUMA node lock in added
> ixgbe_fcoe_lock_init and then have current CPU's numa_node_id
> based NUMA node lock acquired before taking global fcoe->lock.
>
> The node lock is allocated from its NUMA node using kzalloc_node.
>
> Signed-off-by: Vasu Dev <vasu.dev@intel.com>
> Tested-by: Ross Brattain <ross.b.brattain@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> ---
> drivers/net/ixgbe/ixgbe_fcoe.c | 50 ++++++++++++++++++++++++++++++++++++++-
> drivers/net/ixgbe/ixgbe_fcoe.h | 1 +
> 2 files changed, 49 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/ixgbe/ixgbe_fcoe.c b/drivers/net/ixgbe/ixgbe_fcoe.c
> index f5f39ed..aadff4f 100644
> --- a/drivers/net/ixgbe/ixgbe_fcoe.c
> +++ b/drivers/net/ixgbe/ixgbe_fcoe.c
> @@ -109,6 +109,7 @@ int ixgbe_fcoe_ddp_put(struct net_device *netdev, u16 xid)
> len = ddp->len;
> /* if there an error, force to invalidate ddp context */
> if (ddp->err) {
> + spin_lock(fcoe->node_lock[numa_node_id()]);
> spin_lock_bh(&fcoe->lock);
> IXGBE_WRITE_REG(&adapter->hw, IXGBE_FCFLT, 0);
> IXGBE_WRITE_REG(&adapter->hw, IXGBE_FCFLTRW,
> @@ -122,6 +123,7 @@ int ixgbe_fcoe_ddp_put(struct net_device *netdev, u16 xid)
> (xid | IXGBE_FCDMARW_RE));
> fcbuff = IXGBE_READ_REG(&adapter->hw, IXGBE_FCBUFF);
> spin_unlock_bh(&fcoe->lock);
> + spin_unlock(fcoe->node_lock[numa_node_id()]);
> if (fcbuff & IXGBE_FCBUFF_VALID)
> udelay(100);
> }
> @@ -294,6 +296,7 @@ static int ixgbe_fcoe_ddp_setup(struct net_device *netdev, u16 xid,
>
> /* program DMA context */
> hw = &adapter->hw;
> + spin_lock(fcoe->node_lock[numa_node_id()]);
> spin_lock_bh(&fcoe->lock);
>
> /* turn on last frame indication for target mode as FCP_RSPtarget is
> @@ -315,6 +318,7 @@ static int ixgbe_fcoe_ddp_setup(struct net_device *netdev, u16 xid,
> IXGBE_WRITE_REG(hw, IXGBE_FCFLTRW, fcfltrw);
>
> spin_unlock_bh(&fcoe->lock);
> + spin_unlock(fcoe->node_lock[numa_node_id()]);
>
> return 1;
>
> @@ -634,6 +638,42 @@ static void ixgbe_fcoe_ddp_pools_alloc(struct ixgbe_adapter *adapter)
> }
> }
>
> +static void ixgbe_fcoe_locks_free(struct ixgbe_fcoe *fcoe)
> +{
> + int node;
> +
> + if (!fcoe->node_lock)
> + return;
> +
> + for_each_node_with_cpus(node)
> + kfree(fcoe->node_lock[node]);
> +
> + kfree(fcoe->node_lock);
> + fcoe->node_lock = NULL;
> +}
> +
> +static void ixgbe_fcoe_lock_init(struct ixgbe_fcoe *fcoe)
> +{
> + int node;
> + spinlock_t *node_lock;
> +
> + fcoe->node_lock = kzalloc(sizeof(node_lock) * num_possible_nodes(),
> + GFP_KERNEL);
Hmm...
1) Think of what happens if some machine has 3 possible nodes : 0, 2, 3
-> You should use nr_node_ids instead of num_possible_nodes()
2) Make sure this block cant have false sharing : Allocate at least a
full cache line : On a typical 2 node machine, you currently allocate
16bytes of memory, and this small block could share a contended cache
line.
> + if (!fcoe->node_lock)
> + return;
> +
> + for_each_node_with_cpus(node) {
> + node_lock = kzalloc_node(sizeof(*node_lock) , GFP_KERNEL, node);
> + if (!node_lock) {
> + ixgbe_fcoe_locks_free(fcoe);
> + return;
> + }
> + spin_lock_init(node_lock);
> + fcoe->node_lock[node] = node_lock;
> + }
> + spin_lock_init(&fcoe->lock);
> +}
> +
...
>
> /**
> diff --git a/drivers/net/ixgbe/ixgbe_fcoe.h b/drivers/net/ixgbe/ixgbe_fcoe.h
> index d876e7a..8618892 100644
> --- a/drivers/net/ixgbe/ixgbe_fcoe.h
> +++ b/drivers/net/ixgbe/ixgbe_fcoe.h
> @@ -69,6 +69,7 @@ struct ixgbe_fcoe {
> struct pci_pool **pool;
> atomic_t refcnt;
> spinlock_t lock;
> + struct spinlock **node_lock;
Wont this read_mostly pointer sits in often modified cache line ?
> struct ixgbe_fcoe_ddp ddp[IXGBE_FCOE_DDP_MAX];
> unsigned char *extra_ddp_buffer;
> dma_addr_t extra_ddp_buffer_dma;
next prev parent reply other threads:[~2011-06-11 5:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-11 3:02 [net-next 00/13][pull request] Intel Wired LAN Driver Update Jeff Kirsher
2011-06-11 3:02 ` [net-next 01/13] ixgbe: dcbnl reduce duplicated code and indentation Jeff Kirsher
2011-06-11 3:02 ` [net-next 02/13] ixgbe: consolidate packet buffer allocation Jeff Kirsher
2011-06-11 3:02 ` [net-next 03/13] ixgbe: consolidate MRQC and MTQC handling Jeff Kirsher
2011-06-11 3:02 ` [net-next 04/13] ixgbe: configure minimal packet buffers to support TC Jeff Kirsher
2011-06-11 3:02 ` [net-next 05/13] ixgbe: DCB use existing TX and RX queues Jeff Kirsher
2011-06-11 3:02 ` [net-next 06/13] ixgbe: DCB 82598 devices, tx_idx and rx_idx swapped Jeff Kirsher
2011-06-11 3:02 ` [net-next 07/13] ixgbe: setup redirection table for multiple packet buffers Jeff Kirsher
2011-06-11 3:02 ` [net-next 08/13] ixgbe: fix bit mask for DCB version Jeff Kirsher
2011-06-11 3:02 ` [net-next 09/13] ixgbe: DCB and perfect filters can coexist Jeff Kirsher
2011-06-11 3:02 ` [net-next 10/13] ixgbe: DCB, remove unneeded ixgbe_dcb_txq_to_tc() routine Jeff Kirsher
2011-06-11 3:02 ` [net-next 11/13] ixgbe: add support for Dell CEM Jeff Kirsher
2011-06-11 3:02 ` [net-next 12/13] ixgbe: setup per CPU PCI pool for FCoE DDP Jeff Kirsher
2011-06-11 3:02 ` [net-next 13/13] ixgbe: use per NUMA node lock " Jeff Kirsher
2011-06-11 5:18 ` Eric Dumazet [this message]
2011-06-11 5:42 ` Eric Dumazet
2011-06-12 2:00 ` David Miller
2011-06-13 23:59 ` Vasu Dev
2011-06-14 0:02 ` Vasu Dev
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=1307769482.2872.62.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=gospo@redhat.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=vasu.dev@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