All of lore.kernel.org
 help / color / mirror / Atom feed
From: gtolon at inti.gob.ar <gtolon@inti.gob.ar>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Support RSN Mesh
Date: Fri, 02 Dec 2011 13:50:52 -0300	[thread overview]
Message-ID: <4ED901EC.5060202@inti.gob.ar> (raw)
In-Reply-To: <CAEFj985-6zkkJ9t2Voh4B9Qba73-=KysC9kzyGfaLW0g-wphKA@mail.gmail.com>

Hi Chun-Yeow.

El 02/12/2011 12:28 p.m., Yeoh Chun-Yeow escribi?:
> Hi, Gabriel
>
> nohwcrypt=1 will make the ath9k driver to use software crypto instead 
> of hardware crypto. My Atheros chipset is able to support hardware 
> encryption and decryption for CCMP and AES. Thus, when we setup the 
> 802.11s mesh network with security (SAE), the throughput for single 
> hop communication degrades significantly if we use software crypto. We 
> observe the HT throughput when we applied the patch to ensure unicast 
> frame is sent with hardware encryption. However, the throughput is 
> dropped for multi-hop communication. Possible due to the ath9k driver 
> since we have no such problem when security is disable.

Ok, i understand, so if it works well without security it has nothing to 
do with the problem i mentioned.

>
> Regarding the adhoc batman-adv, did you setup the adhoc mode using 
> security such as WPA2? What is the performance that you obtained?
>
> Regards,
> Chun-Yeow

We are not using security yet, because we are having problems with 
throughput tests without encryption, and it's difficult to find where 
the problem is.

Regards

Gabriel

>
>
> On Fri, Dec 2, 2011 at 9:26 PM, <gtolon@inti.gob.ar 
> <mailto:gtolon@inti.gob.ar>> wrote:
>
>     Hi Chun-Yeow
>
>     I don't know if this is usefull for you, but we are using ad hoc
>     with batman-adv, and we had some problems when the nodes didn't
>     choose good routes for high throughputs for relatively long
>     distances. Asking to the batman-adv list they explained us that
>     the algorithm to choose the routes is based on low rate
>     broadcasts, so the nodes could choose routes that with high rates
>     become bad. They suggested us to increase the multicast rates, so
>     that the nodes could "realize" if a route were not good for high
>     throughputs, and it worked better, the nodes chose routes with
>     more hops for long distances getting a better throughput than
>     using less hops with larger distances.
>
>     By the way, why with nohwcrypt=1 the throughput get worse?
>
>     Regards
>
>     Gabriel
>

  reply	other threads:[~2011-12-02 16:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-02  8:51 [ath9k-devel] [PATCH] ath9k: Support RSN Mesh Yeoh Chun-Yeow
2011-12-02  9:18 ` Mohammed Shafi
2011-12-02  9:23   ` Yeoh Chun-Yeow
2011-12-02  9:38     ` Mohammed Shafi
2011-12-02  9:51       ` Yeoh Chun-Yeow
2011-12-02  9:54         ` Yeoh Chun-Yeow
2011-12-02 10:01         ` Mohammed Shafi
2011-12-02 10:04           ` Yeoh Chun-Yeow
2011-12-02 10:12             ` Mohammed Shafi
2011-12-02 13:26             ` gtolon at inti.gob.ar
2011-12-02 15:28               ` Yeoh Chun-Yeow
2011-12-02 16:50                 ` gtolon at inti.gob.ar [this message]
2011-12-07  5:16                   ` Yeoh Chun-Yeow
  -- strict thread matches above, loose matches on Subject: below --
2011-12-07 20:45 Thomas Pedersen
2011-12-07 21:31 ` Luis R. Rodriguez

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=4ED901EC.5060202@inti.gob.ar \
    --to=gtolon@inti.gob.ar \
    --cc=ath9k-devel@lists.ath9k.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.