linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [RFC][RFT] mac80211 / mesh: Modularize Path Selection Protocol
@ 2009-01-26 20:22 Florian Sesser
  2009-01-26 20:37 ` [PATCH 1/1] Added capability to get/set individual mesh IDs Florian Sesser
                   ` (2 more replies)
  0 siblings, 3 replies; 16+ messages in thread
From: Florian Sesser @ 2009-01-26 20:22 UTC (permalink / raw)
  To: linux-wireless

Hi all!

As I mentioned some time ago on linux-wireless [1], I am trying to
extend o11s so I can include Scalable Source Routing. Towards that goal,
I first need a method to be able to exchange the used mesh path
selection protocol.

In this patch series, you can see my first approach to an API that
enables users to exchange the path selection protocol at runtime.

What I have done so far is mostly borrowing source code from
block/elevator.c for most of the registration, finding and inserting
glue code. Also, I have wrapped mesh_hwmp into an own module and written
a test module (pptest) so the module switching can be tried out. To that
end, I also have patched iw.

For completeness, I will post the patch to iw in reply to this eMail on
this list, as it is quite simple, short and affects only two files
(compared to 14 or so for the API in the kernel).

This is my first patch not only to the kernel, but to any open source
project, so please be gentle ;) I am open to suggestions for
improvement; please also remind me on any coding style or other errors
you may find.

I would be very glad if some of the experts here could review it and
give me advice on:

 * If my selection of functions for the abstraction ops-struct is
somewhat sane or if I am missing critical parts (this is most important
to me)

 * Which is the best location for the path selection protocol ID
(cfg80211 and iw suggest having the value in struct mesh_params. o11s
currently stores it in ieee80211_if_mesh->mesh_pp_id, which is in use at
least by mesh_matches_local. And finally it obviously needs to be stored
in the path selection protocol modules.)

Greetings from Munich!

Florian


[1] http://marc.info/?l=linux-wireless&m=122600107811517&w=2


^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2009-01-27 11:22 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-01-26 20:22 [RFC][RFT] mac80211 / mesh: Modularize Path Selection Protocol Florian Sesser
2009-01-26 20:37 ` [PATCH 1/1] Added capability to get/set individual mesh IDs Florian Sesser
2009-01-26 20:39 ` [PATCH 1/6] mac80211: Virtualize mesh path selection ops Florian Sesser
2009-01-26 20:39   ` [PATCH 2/6] mac80211: Registration of path selection protocols Florian Sesser
2009-01-26 20:39   ` [PATCH 3/6] mac80211: Modularized mesh_hwmp.c Florian Sesser
2009-01-26 21:20     ` Johannes Berg
2009-01-26 20:39   ` [PATCH 4/6] mac80211: More small changes for modularization Florian Sesser
2009-01-26 21:16     ` Johannes Berg
2009-01-27 11:15       ` Florian Sesser
2009-01-27 11:19         ` Johannes Berg
2009-01-27 11:22         ` Johannes Berg
2009-01-26 20:39   ` [PATCH 5/6] mac80211: o11s PP api communication with userspace Florian Sesser
2009-01-26 20:39   ` [PATCH 6/6] mac80211: Path Selection Protocol dummy module Florian Sesser
2009-01-26 21:19     ` Johannes Berg
2009-01-27  9:33   ` [PATCH 1/6] mac80211: Virtualize mesh path selection ops Rami Rosen
2009-01-26 21:09 ` [RFC][RFT] mac80211 / mesh: Modularize Path Selection Protocol Johannes Berg

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).