From: Eric Dumazet <eric.dumazet@gmail.com>
To: "Pradeep A. Dalvi" <netdev@pradeepdalvi.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH net] amd/lance.c: dev_alloc_skb to netdev_alloc_skb
Date: Wed, 25 Jan 2012 19:55:06 +0100 [thread overview]
Message-ID: <1327517706.2605.7.camel@edumazet-laptop> (raw)
In-Reply-To: <1327517188-14088-1-git-send-email-netdev@pradeepdalvi.com>
Le jeudi 26 janvier 2012 à 00:16 +0530, Pradeep A. Dalvi a écrit :
> Replaced deprecating dev_alloc_skb with netdev_alloc_skb for amd/lance.c
> - Removed extra skb->dev = dev
>
> Signed-off-by: Pradeep A. Dalvi <netdev@pradeepdalvi.com>
> ---
> drivers/net/ethernet/amd/lance.c | 9 ++++-----
> 1 files changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/ethernet/amd/lance.c b/drivers/net/ethernet/amd/lance.c
> index a6e2e84..a8a6b45 100644
> --- a/drivers/net/ethernet/amd/lance.c
> +++ b/drivers/net/ethernet/amd/lance.c
> @@ -871,12 +871,11 @@ lance_init_ring(struct net_device *dev, gfp_t gfp)
> struct sk_buff *skb;
> void *rx_buff;
>
> - skb = alloc_skb(PKT_BUF_SZ, GFP_DMA | gfp);
> + skb = __netdev_alloc_skb(dev, PKT_BUF_SZ, GFP_DMA | gfp);
Nack
As I already explained, alloc_skb() and netdev_alloc_skb() are
different.
Why do you repost this ?
nedev_alloc_skb() adds NET_SKB_PAD bytes.
This driver doesnt need this extra space.
(In fact it could use kmalloc(), since the skb themselves are not used
at all : At RX time, we perform a copybreak)
next prev parent reply other threads:[~2012-01-25 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 18:46 [PATCH net] amd/lance.c: dev_alloc_skb to netdev_alloc_skb Pradeep A. Dalvi
2012-01-25 18:55 ` Eric Dumazet [this message]
2012-01-25 20:01 ` Pradeep A. Dalvi
2012-01-25 20:16 ` Eric Dumazet
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=1327517706.2605.7.camel@edumazet-laptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@pradeepdalvi.com \
--cc=netdev@vger.kernel.org \
/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