From: Eric Dumazet <eric.dumazet@gmail.com>
To: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
Cc: davem@davemloft.net, netdev@vger.kernel.org, eugenia@mellanox.co.il
Subject: Re: [PATCH 13/14] mlx4_en: Moving to work with GRO
Date: Sat, 28 Aug 2010 12:56:14 +0200 [thread overview]
Message-ID: <1282992974.2277.17.camel@edumazet-laptop> (raw)
In-Reply-To: <4C73CD46.10907@mellanox.co.il>
Le mardi 24 août 2010 à 16:46 +0300, Yevgeny Petrilin a écrit :
> Signed-off-by: Yevgeny Petrilin <yevgenyp@mellanox.co.il>
> ---
> drivers/net/mlx4/en_ethtool.c | 58 +---------------------------------
> drivers/net/mlx4/en_main.c | 5 ---
> drivers/net/mlx4/en_netdev.c | 3 +-
> drivers/net/mlx4/en_rx.c | 68 ++++++++---------------------------------
> drivers/net/mlx4/en_tx.c | 1 +
> drivers/net/mlx4/mlx4_en.h | 6 ---
> 6 files changed, 17 insertions(+), 124 deletions(-)
>
> err_hwq:
> mlx4_free_hwq_res(mdev->dev, &ring->wqres, ring->buf_size);
> err_ring:
> @@ -412,7 +380,6 @@ void mlx4_en_destroy_rx_ring(struct mlx4_en_priv *priv,
> {
> struct mlx4_en_dev *mdev = priv->mdev;
>
> - kfree(ring->lro.lro_arr);
> mlx4_en_unmap_buffer(&ring->wqres.buf);
> mlx4_free_hwq_res(mdev->dev, &ring->wqres, ring->buf_size + TXBB_SIZE);
> vfree(ring->rx_info);
> @@ -563,7 +530,6 @@ int mlx4_en_process_rx_cq(struct net_device *dev, struct mlx4_en_cq *cq, int bud
> struct mlx4_cqe *cqe;
> struct mlx4_en_rx_ring *ring = &priv->rx_ring[cq->ring];
> struct skb_frag_struct *skb_frags;
> - struct skb_frag_struct lro_frags[MLX4_EN_MAX_RX_FRAGS];
> struct mlx4_en_rx_desc *rx_desc;
> struct sk_buff *skb;
> int index;
> @@ -623,37 +589,33 @@ int mlx4_en_process_rx_cq(struct net_device *dev, struct mlx4_en_cq *cq, int bud
> * - TCP/IP (v4)
> * - without IP options
> * - not an IP fragment */
> - if (mlx4_en_can_lro(cqe->status) &&
> - dev->features & NETIF_F_LRO) {
> + if (dev->features & NETIF_F_GRO) {
> + struct sk_buff *gro_skb = napi_get_frags(&cq->napi);
>
napi_get_frags() can return NULL, please fix your driver.
> nr = mlx4_en_complete_rx_desc(
> priv, rx_desc,
> - skb_frags, lro_frags,
> + skb_frags, skb_shinfo(gro_skb)->frags,
> ring->page_alloc, length);
> if (!nr)
> goto next;
>
Thanks
prev parent reply other threads:[~2010-08-28 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 13:46 [PATCH 13/14] mlx4_en: Moving to work with GRO Yevgeny Petrilin
2010-08-28 10:56 ` Eric Dumazet [this message]
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=1282992974.2277.17.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=eugenia@mellanox.co.il \
--cc=netdev@vger.kernel.org \
--cc=yevgenyp@mellanox.co.il \
/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