From: Luis Carlos Cobo <luisca@cozybit.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 04/13 v2] o11s: added mesh.h, mesh function and data structures definitions
Date: Mon, 25 Feb 2008 11:16:18 -0800 [thread overview]
Message-ID: <1203966978.6929.11.camel@localhost> (raw)
In-Reply-To: <1203697425.7082.70.camel@johannes.berg>
On Fri, 2008-02-22 at 17:23 +0100, Johannes Berg wrote:
> I don't think I fully understand that. The mesh path points to a sta
> structure, so when that sta is removed, the corresponding mesh path must
> also be deleted. I think I need to look closer at where that is done to
> understand how it could be substituted.
In sta_info_free() we call mesh_plink_deactivate(sta), which calls
mesh_path_flush_by_nexthop(). There is where you could substitute the
mesh path (copy it with next_hop pointing to NULL, substitute pointer,
rcu_synchronize()). However there is not much to gain. Since mesh paths
are freed if inactive sooner than mesh peer links are, this will
actually only happen when mesh peer links are either deleted from user
land or because a specific "peer link close" frame is received.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-02-25 19:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-22 4:08 [PATCH 04/13 v2] o11s: added mesh.h, mesh function and data structures definitions Luis Carlos Cobo
2008-02-22 16:23 ` Johannes Berg
2008-02-25 19:16 ` Luis Carlos Cobo [this message]
2008-02-25 19:18 ` 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=1203966978.6929.11.camel@localhost \
--to=luisca@cozybit.com \
--cc=johannes@sipsolutions.net \
--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