Linux wireless drivers development
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Luis Carlos Cobo <luisca@cozybit.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 04/13 v2] o11s: added mesh.h, mesh function and data structures definitions
Date: Fri, 22 Feb 2008 17:23:44 +0100	[thread overview]
Message-ID: <1203697425.7082.70.camel@johannes.berg> (raw)
In-Reply-To: <47be7732.20588c0a.0360.ffff8f1c@mx.google.com> (sfid-20080222_071816_353396_9A4A9995)

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]


On Thu, 2008-02-21 at 20:08 -0800, Luis Carlos Cobo wrote:
> 
> + *
> + * The combination of dst and dev is unique in the mesh path table. A reference
> + * to the next_hop sta will be kept and in case this sta is removed, the
> + * mesh_path structure must be also removed or substitued in a rcu safe way
> + */

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.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2008-02-22 16:23 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 [this message]
2008-02-25 19:16   ` Luis Carlos Cobo
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=1203697425.7082.70.camel@johannes.berg \
    --to=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