From: Florian Sesser <flomaillist@cosetrain.com>
To: linux-wireless@vger.kernel.org
Subject: o11s: Modularize Path Selection Protocol etc.
Date: Mon, 21 Dec 2009 16:50:08 +0100 [thread overview]
Message-ID: <4B2F9930.8070401@cosetrain.com> (raw)
Hi mesh folks!
For my diploma thesis, I want to add a P2P routing protocoll to the
pre-80211s software in the linux kernel. For details, see my previous
mails. [1],[2]
In struct ieee80211_if_mesh, the current code reads
net/mac80211/ieee80211_i.h
> u8 mesh_id[IEEE80211_MAX_MESH_ID_LEN];
> size_t mesh_id_len;
> /* Active Path Selection Protocol Identifier */
> u8 mesh_pp_id;
> /* Active Path Selection Metric Identifier */
> u8 mesh_pm_id;
> /* Congestion Control Mode Identifier */
> u8 mesh_cc_id;
> /* Synchronization Protocol Identifier */
> u8 mesh_sp_id;
> /* Authentication Protocol Identifier */
> u8 mesh_auth_id;
which is what I at first wanted to work with.
In my last patch [2], I introduced some new 32 bit struct members,
because, if I am not mistaken, these IDs should include a vendor
specific OUI, which enables a user to combine a path selection protocol
of vendor A with a path selection metric of vendor B.
So.. am I erring here?
If yes, I would introduce a new 24 bit value for the OUI, which will be
combined with all the above u8's before going over the wire (into the
air of course)
...if no, I would replace those values by 32 bit ones, possibly even
braking ABI compatibility.
What do you think?
Do you maybe have a better suggestion?
Thank you very much for your input!
Florian
[1] http://marc.info/?l=linux-wireless&m=122600107811517&w=2
[2] http://marc.info/?l=linux-wireless&m=123300309207545&w=2
next reply other threads:[~2009-12-21 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 15:50 Florian Sesser [this message]
2009-12-21 16:17 ` o11s: Modularize Path Selection Protocol etc Rui Paulo
2009-12-22 8:33 ` Simon Raffeiner
2009-12-22 11:55 ` Florian Sesser
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=4B2F9930.8070401@cosetrain.com \
--to=flomaillist@cosetrain.com \
--cc=linux-wireless@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).