From: Simon Wunderlich <sw@simonwunderlich.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] [PATCH 0/2] Fragments and QoS
Date: Tue, 10 May 2016 16:23:56 +0200 [thread overview]
Message-ID: <6446352.pcAao2qlWC@prime> (raw)
In-Reply-To: <1462817016-17867-1-git-send-email-andrew@lunn.ch>
[-- Attachment #1: Type: text/plain, Size: 741 bytes --]
On Monday 09 May 2016 20:03:34 Andrew Lunn wrote:
> BATMAN currently does not allow QoS policies to be used with
> fragmented packets. The first patch copies the skb priority from the
> unfragmented packet into the fragments as they are built, so the lower
> layers can then prioritise as appropriated.
>
> The second patch places the priority into the fragment header, and
> upon reception of a fragment, copies it into the skb priority, so that
> when the fragment is retransmitted, it is correctly prioritised.
>
> Andrew Lunn (2):
> batman-adv: Set skb priority in fragments
> batman-adv: Include frame priority in fragment header
Series looks good to me.
Reviewed-by: Simon Wunderlich <sw@simonwunderlich.de>
Thanks,
Simon
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2016-05-10 14:23 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
2016-05-10 14:23 ` Simon Wunderlich [this message]
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=6446352.pcAao2qlWC@prime \
--to=sw@simonwunderlich.de \
--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.