All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Lindner <mareklindner@neomailbox.ch>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Include frame priority in fragment header
Date: Thu, 12 May 2016 18:04:38 +0800	[thread overview]
Message-ID: <3966287.AqV7F3pn4W@voltaire> (raw)
In-Reply-To: <1462817016-17867-3-git-send-email-andrew@lunn.ch>

[-- Attachment #1: Type: text/plain, Size: 728 bytes --]

On Monday, May 09, 2016 20:03:36 Andrew Lunn wrote:
> Unfragmented frames which traverse a node have their skb->priority set
> by looking at the IP ToS byte, or the 802.1p header. However for
> fragments this is not possible, only one of the fragments will contain
> the headers. Instead, place the priority into the fragment header and
> on receiving a fragment, use this information to set the skb->priority
> for when the fragment is forwarded.
> 
> Signed-off-by: Andrew Lunn <andrew@lunn.ch>
> ---
>  net/batman-adv/fragmentation.c | 2 ++
>  net/batman-adv/packet.h        | 7 +++++--
>  net/batman-adv/routing.c       | 2 ++
>  3 files changed, 9 insertions(+), 2 deletions(-)

Applied in revision 4f241fc.

Thanks,
Marek

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2016-05-12 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 18:03 [B.A.T.M.A.N.] [PATCH 0/2] Fragments and QoS Andrew Lunn
2016-05-09 18:03 ` [B.A.T.M.A.N.] [PATCH 1/2] batman-adv: Set skb priority in fragments Andrew Lunn
2016-05-11  6:21   ` Sven Eckelmann
2016-05-11  8:06   ` Marek Lindner
2016-05-09 18:03 ` [B.A.T.M.A.N.] [PATCH 2/2] batman-adv: Include frame priority in fragment header Andrew Lunn
2016-05-12 10:04   ` Marek Lindner [this message]
2016-05-10 14:23 ` [B.A.T.M.A.N.] [PATCH 0/2] Fragments and QoS Simon Wunderlich

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=3966287.AqV7F3pn4W@voltaire \
    --to=mareklindner@neomailbox.ch \
    --cc=b.a.t.m.a.n@lists.open-mesh.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.