From: Ido Schimmel <idosch@idosch.org>
To: Ryota Ozaki <ozaki.ryota@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] doc: fix wrongly referencing dev->skb_mark
Date: Mon, 10 Oct 2016 16:49:43 +0300 [thread overview]
Message-ID: <20161010134943.GA8090@splinter> (raw)
In-Reply-To: <1476098139-6333-1-git-send-email-ozaki.ryota@gmail.com>
Hi,
On Mon, Oct 10, 2016 at 08:15:39PM +0900, Ryota Ozaki wrote:
> Section "Flooding L2 domain" says, to avoid duplicated flooding, if
> skb->offload_fwd_mark is matched with dev->skb_mark, the kernel will
> drop the packet. However, the relevant code in __dev_queue_xmit
> compares skb->offload_fwd_mark with dev->offload_fwd_mark, not
> dev->skb_mark. I guess the text is wrong.
>
> Signed-off-by: Ryota Ozaki <ozaki.ryota@gmail.com>
> ---
> Documentation/networking/switchdev.txt | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/networking/switchdev.txt b/Documentation/networking/switchdev.txt
> index 31c3911..d4124a0 100644
> --- a/Documentation/networking/switchdev.txt
> +++ b/Documentation/networking/switchdev.txt
> @@ -286,8 +286,8 @@ otherwise there will be duplicate packets on the wire.
> To avoid duplicate packets, the device/driver should mark a packet as already
> forwarded using skb->offload_fwd_mark. The same mark is set on the device
> ports in the domain using dev->offload_fwd_mark. If the skb->offload_fwd_mark
> -is non-zero and matches the forwarding egress port's dev->skb_mark, the kernel
> -will drop the skb right before transmit on the egress port, with the
> +is non-zero and matches the forwarding egress port's dev->offload_fwd_mark,
> +the kernel will drop the skb right before transmit on the egress port, with the
I think your tree isn't up to date. The flooding mechanism (and this
document) were modified in commit 6bc506b4fb06 ("bridge: switchdev: Add
forward mark support for stacked devices")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=6bc506b4fb065eac3d89ca1ce37082e174493d9e
Also, in the future, please specify to which tree (net, net-next) your
patch should go. See:
https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt
(under "How do I indicate which tree (net vs. net-next) my patch
should be in?").
Thanks!
> understanding that the device already forwarded the packet on same egress port.
> The driver can use switchdev_port_fwd_mark_set() to set a globally unique mark
> for port's dev->offload_fwd_mark, based on the port's parent ID (switch ID) and
> --
> 2.7.4
>
next prev parent reply other threads:[~2016-10-10 13:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 11:15 [PATCH] doc: fix wrongly referencing dev->skb_mark Ryota Ozaki
2016-10-10 13:49 ` Ido Schimmel [this message]
2016-10-11 15:47 ` Ryota Ozaki
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=20161010134943.GA8090@splinter \
--to=idosch@idosch.org \
--cc=netdev@vger.kernel.org \
--cc=ozaki.ryota@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 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.