Netdev List
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: davem@davemloft.net, zajec5@gmail.com, netdev@vger.kernel.org
Subject: Re: [PATCH] bgmac: fix unaligned accesses to network headers
Date: Sat, 16 Feb 2013 10:36:12 -0800	[thread overview]
Message-ID: <20130216103612.190d908e@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1361025154-11612-1-git-send-email-hauke@hauke-m.de>

On Sat, 16 Feb 2013 15:32:34 +0100
Hauke Mehrtens <hauke@hauke-m.de> wrote:

> Without this patch I get many unaligned access warnings per packet,
> this patches fixes them all. This should improve performance ony some
> systems like mips.
> 
> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
>  drivers/net/ethernet/broadcom/bgmac.c |    3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/net/ethernet/broadcom/bgmac.c b/drivers/net/ethernet/broadcom/bgmac.c
> index d341090..f9b1bc8 100644
> --- a/drivers/net/ethernet/broadcom/bgmac.c
> +++ b/drivers/net/ethernet/broadcom/bgmac.c
> @@ -301,8 +301,9 @@ static int bgmac_dma_rx_read(struct bgmac *bgmac, struct bgmac_dma_ring *ring,
>  			bgmac_err(bgmac, "Found poisoned packet at slot %d, DMA issue!\n",
>  				  ring->start);
>  		} else {
> -			new_skb = netdev_alloc_skb(bgmac->net_dev, len);
> +			new_skb = netdev_alloc_skb(bgmac->net_dev, len + 2);
>  			if (new_skb) {
> +				skb_reserve(new_skb, 2);
>  				skb_put(new_skb, len);
>  				skb_copy_from_linear_data_offset(skb, BGMAC_RX_FRAME_OFFSET,
>  								 new_skb->data,

NAK. Use netdev_alloc_skb_ip_align instead. 
It is less error prone, and handles case of architectures where unaligned is faster.

  reply	other threads:[~2013-02-16 18:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-16 14:32 [PATCH] bgmac: fix unaligned accesses to network headers Hauke Mehrtens
2013-02-16 18:36 ` Stephen Hemminger [this message]
2013-02-16 19:01   ` Hauke Mehrtens
2013-02-18 16:14 ` Rafał Miłecki

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=20130216103612.190d908e@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber.org \
    --cc=davem@davemloft.net \
    --cc=hauke@hauke-m.de \
    --cc=netdev@vger.kernel.org \
    --cc=zajec5@gmail.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