Linux wireless drivers development
 help / color / mirror / Atom feed
From: Felix Fietkau <nbd@openwrt.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Luis Carlos Cobo <luisca@cozybit.com>, linux-wireless@vger.kernel.org
Subject: Re: [PATCH 4/7] o80211s: (mac80211s) basic mesh interface support
Date: Fri, 02 Nov 2007 11:02:02 +0100	[thread overview]
Message-ID: <472AF59A.4020302@openwrt.org> (raw)
In-Reply-To: <1193997288.12078.39.camel@johannes.berg>

Johannes Berg wrote:
>> Agreed about filename length. I would prefer not to make mesh
>> networking configurable, as STA, IBSS, etc modes aren't configurable
>> either. I prefer to avoid polluting the data path with ifdefs.
> 
> Ok, I'm not sure, it just seems like quite a bit of code especially when
> all the other features will be added, something people like the OpenWRT
> folks might not like. nbd?
Depends on how big it is. I think merging it without ifdefs is fine for
now. If it gets too big, we can make some ifdef patches later.

>> Mesh APs are not supported yet, but we plan to support them through a
>> different interface type (e.g.  ..._TYPE_MAP) or extending the AP
>> interface type. Mesh STAs and APs will share all the mesh-specific
>> stuff (peer link discovery, path discovery, etc) but they have little
>> in common in the data path, so I do not think it makes sense to use
>> the same interface type for both. Maybe I should rename ..IF_TYPE_MESH
>> to ..IF_TYPE_MESH_STA?
> 
> Probably. Come to think of it, how much mesh networking is actually done
> by the mesh AP? I guess we need to support this in hostapd rather than
> the kernel?
If we're forced to use hostapd for starting the mesh networking, then that
would probably be a bigger source of bloat than the mesh code itself :)

- Felix

  reply	other threads:[~2007-11-02 10:02 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-30  1:04 [PATCH 4/7] o80211s: (mac80211s) basic mesh interface support Luis Carlos Cobo
2007-10-31 12:16 ` Johannes Berg
2007-11-01  0:36   ` Luis Carlos Cobo
2007-11-02  9:54     ` Johannes Berg
2007-11-02 10:02       ` Felix Fietkau [this message]
2007-11-02 10:15         ` Johannes Berg
2007-10-31 12:22 ` Dan Williams
2007-11-01  0:21   ` Luis Carlos Cobo
2007-11-02 10:20     ` Johannes Berg

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=472AF59A.4020302@openwrt.org \
    --to=nbd@openwrt.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luisca@cozybit.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox