netdev - Re: [net-2.6 PATCH V2] mlx4_en: Fix a kernel panic when waking tx queue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4A1BC8E4.1050009@cosmosbay.com>
Date:	Tue, 26 May 2009 12:48:04 +0200
From:	Eric Dumazet <dada1@...mosbay.com>
To:	Yevgeny Petrilin <yevgenyp@...lanox.co.il>
CC:	David Miller <davem@...emloft.net>, netdev@...r.kernel.org,
	tziporet@...lanox.co.il
Subject: Re: [net-2.6 PATCH V2] mlx4_en: Fix a kernel panic when waking tx
 queue

Yevgeny Petrilin a écrit :
> When the transmit queue gets full we enable interrupts for TX completions
> There was a race that we handled the TX queue both from the interrupt context
> and from the transmit function. Using "spin_trylock_irq()" ensures this
> doesn't happen.
> 
> Signed-off-by: Yevgeny Petrilin <yevgenyp@...lanox.co.il>
> ---
>  drivers/net/mlx4/en_tx.c |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/mlx4/en_tx.c b/drivers/net/mlx4/en_tx.c
> index ac6fc49..e5c98a9 100644
> --- a/drivers/net/mlx4/en_tx.c
> +++ b/drivers/net/mlx4/en_tx.c
> @@ -426,7 +426,7 @@ void mlx4_en_poll_tx_cq(unsigned long data)
> 
>  	INC_PERF_COUNTER(priv->pstats.tx_poll);
> 
> -	if (!spin_trylock(&ring->comp_lock)) {
> +	if (!spin_trylock_irq(&ring->comp_lock)) {
>  		mod_timer(&cq->timer, jiffies + MLX4_EN_TX_POLL_TIMEOUT);
>  		return;
>  	}
> @@ -439,7 +439,7 @@ void mlx4_en_poll_tx_cq(unsigned long data)
>  	if (inflight && priv->port_up)
>  		mod_timer(&cq->timer, jiffies + MLX4_EN_TX_POLL_TIMEOUT);
> 
> -	spin_unlock(&ring->comp_lock);
> +	spin_unlock_irq(&ring->comp_lock);
>  }
> 
>  static struct mlx4_en_tx_desc *mlx4_en_bounce_to_desc(struct mlx4_en_priv *priv,
> @@ -482,9 +482,9 @@ static inline void mlx4_en_xmit_poll(struct mlx4_en_priv *priv, int tx_ind)
> 
>  	/* Poll the CQ every mlx4_en_TX_MODER_POLL packets */
>  	if ((++ring->poll_cnt & (MLX4_EN_TX_POLL_MODER - 1)) == 0)
> -		if (spin_trylock(&ring->comp_lock)) {
> +		if (spin_trylock_irq(&ring->comp_lock)) {
>  			mlx4_en_process_tx_cq(priv->dev, cq);
> -			spin_unlock(&ring->comp_lock);
> +			spin_unlock_irq(&ring->comp_lock);
>  		}
>  }
> 

Just curious.

Blocking hard IRQ while doing TX completion is quite nasty,
as freeing one hundred of skb take long.

Could you try something in process context instead ?

Is this timer driven tx completion thing really good for performance ?


static inline void mlx4_en_xmit_poll(struct mlx4_en_priv *priv, int tx_ind)
{
        struct mlx4_en_cq *cq = &priv->tx_cq[tx_ind];
        struct mlx4_en_tx_ring *ring = &priv->tx_ring[tx_ind];

        /* If we don't have a pending timer, set one up to catch our recent
           post in case the interface becomes idle */
        if (!timer_pending(&cq->timer))
                mod_timer(&cq->timer, jiffies + MLX4_EN_TX_POLL_TIMEOUT);


        /* Poll the CQ every mlx4_en_TX_MODER_POLL packets */
        if ((++ring->poll_cnt & (MLX4_EN_TX_POLL_MODER - 1)) == 0)
                if (spin_trylock(&ring->comp_lock)) {
                        mlx4_en_process_tx_cq(priv->dev, cq);
                        spin_unlock(&ring->comp_lock);
                }
}


One interesting thing is calling mlx4_en_process_tx_cq() once every 16 packets,
this means the producer cpu is also the cpu doing the TX completion, I like this.

--
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