netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Amir Vadai <amirv@mellanox.com>, "David S. Miller" <davem@davemloft.net>
Cc: Alexander Duyck <alexander.h.duyck@intel.com>,
	netdev@vger.kernel.org, Or Gerlitz <ogerlitz@mellanox.com>,
	Yevgeny Petrilin <yevgenyp@mellanox.com>,
	Ido Shamay <idos@mellanox.com>
Subject: Re: [PATCH net-next 2/2] net/mlx4_en: Copy exact header to SKB linear part
Date: Mon, 28 Jul 2014 14:56:46 +0400	[thread overview]
Message-ID: <53D62C6E.7050604@cogentembedded.com> (raw)
In-Reply-To: <1406542451-8857-3-git-send-email-amirv@mellanox.com>

Hello.

On 07/28/2014 02:14 PM, Amir Vadai wrote:

> Based on patch from Eric Dumazet
> When copy received packet header to the linear section of the SKB,

    s/copy/copying/.

> Copy the exact header (best effort) and not the max possible header,

    s/Copy/copy/.

> using the new network helper function __net_get_headlen.

    Not eth_frame_headlen()?

> It will return the size of the header up to the latest known header.

> Signed-off-by: Ido Shamay <idos@mellanox.com>
> Signed-off-by: Amir Vadai <amirv@mellanox.com>
> ---
>   drivers/net/ethernet/mellanox/mlx4/en_rx.c | 13 ++++++++-----
>   1 file changed, 8 insertions(+), 5 deletions(-)

> diff --git a/drivers/net/ethernet/mellanox/mlx4/en_rx.c b/drivers/net/ethernet/mellanox/mlx4/en_rx.c
> index 9c909d2..c4471f1 100644
> --- a/drivers/net/ethernet/mellanox/mlx4/en_rx.c
> +++ b/drivers/net/ethernet/mellanox/mlx4/en_rx.c
> @@ -588,6 +588,7 @@ static struct sk_buff *mlx4_en_rx_skb(struct mlx4_en_priv *priv,
>   		skb_copy_to_linear_data(skb, va, length);
>   		skb->tail += length;
>   	} else {
> +		unsigned int hlen;

    Empty line needed here.

>   		/* Move relevant fragments to skb */
>   		used_frags = mlx4_en_complete_rx_desc(priv, rx_desc, frags,
>   							skb, length);

WBR, Sergei

  reply	other threads:[~2014-07-28 10:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 10:14 [PATCH net-next 0/2] Helper to find length of headers in an ethernet frame Amir Vadai
2014-07-28 10:14 ` [PATCH net-next 1/2] net: Header length compution function Amir Vadai
2014-07-30  4:58   ` David Miller
2014-07-30  7:00     ` Eric Dumazet
2014-07-30 14:26       ` Alexander Duyck
2014-07-31  1:39         ` David Miller
2014-07-31 15:34           ` Alexander Duyck
2014-08-23 19:19             ` David Miller
2014-08-25 22:21               ` Alexander Duyck
2014-08-25 22:32                 ` David Miller
2014-07-31  1:34       ` David Miller
2014-07-28 10:14 ` [PATCH net-next 2/2] net/mlx4_en: Copy exact header to SKB linear part Amir Vadai
2014-07-28 10:56   ` Sergei Shtylyov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-08 12:50 [PATCH net-next 0/2] net, igb, mlx4: Copy exact header to SKB linear buffer Amir Vadai
2014-05-08 12:50 ` [PATCH net-next 2/2] net/mlx4_en: Copy exact header to SKB linear part Amir Vadai

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=53D62C6E.7050604@cogentembedded.com \
    --to=sergei.shtylyov@cogentembedded.com \
    --cc=alexander.h.duyck@intel.com \
    --cc=amirv@mellanox.com \
    --cc=davem@davemloft.net \
    --cc=idos@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=yevgenyp@mellanox.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;
as well as URLs for NNTP newsgroup(s).