All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Ard Biesheuvel <ardb@kernel.org>
Cc: netdev@vger.kernel.org, linux-omap@vger.kernel.org,
	arnd@arndb.de, davem@davemloft.net, kuba@kernel.org,
	grygorii.strashko@ti.com, ilias.apalodimas@linaro.org
Subject: Re: [PATCH net] net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
Date: Wed, 19 Jan 2022 14:20:10 +0000	[thread overview]
Message-ID: <164260201057.5270.6115220828314624622.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220118102204.1258645-1-ardb@kernel.org>

Hello:

This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:

On Tue, 18 Jan 2022 11:22:04 +0100 you wrote:
> Both versions of the CPSW driver declare a CPSW_HEADROOM_NA macro that
> takes NET_IP_ALIGN into account, but fail to use it appropriately when
> storing incoming packets in memory. This results in the IPv4 source and
> destination addresses to appear misaligned in memory, which causes
> aligment faults that need to be fixed up in software.
> 
> So let's switch from CPSW_HEADROOM to CPSW_HEADROOM_NA where needed.
> This gets rid of any alignment faults on the RX path on a Beaglebone
> White.
> 
> [...]

Here is the summary with links:
  - [net] net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account
    https://git.kernel.org/netdev/net/c/1771afd47430

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



  parent reply	other threads:[~2022-01-19 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-18 10:22 [PATCH net] net: cpsw: avoid alignment faults by taking NET_IP_ALIGN into account Ard Biesheuvel
2022-01-18 13:14 ` Ilias Apalodimas
2022-01-18 21:03 ` Jakub Kicinski
2022-01-18 21:32   ` Ard Biesheuvel
2022-01-19 14:20 ` patchwork-bot+netdevbpf [this message]
2022-01-19 14:25 ` Alexey Smirnov
2022-01-19 15:56   ` Ard Biesheuvel

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=164260201057.5270.6115220828314624622.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ardb@kernel.org \
    --cc=arnd@arndb.de \
    --cc=davem@davemloft.net \
    --cc=grygorii.strashko@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=kuba@kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.