All of lore.kernel.org
 help / color / mirror / Atom feed
From: mabbas <mabbas@linux.intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: Jouni Malinen <jkm@devicescape.com>, netdev@vger.kernel.org
Subject: Re: [PATCH 2/7] d80211: add support for SIOCSIWRATE and SIOCGIWRATE
Date: Thu, 21 Sep 2006 09:59:39 -0700	[thread overview]
Message-ID: <4512C4FB.5010704@linux.intel.com> (raw)
In-Reply-To: <20060921184021.1fb7fa6e@logostar.upir.cz>

Jiri Benc wrote:
> On Wed, 30 Aug 2006 10:19:19 -0700, Jouni Malinen wrote:
>   
>> On Mon, Aug 28, 2006 at 01:45:34PM -0700, mabbas wrote:
>>
>>     
>>> This patch modify d80211 to add SIOCSIWRATE and SIOCGIWRATE
>>> commands. this patch almost does the same thing as in 
>>> PRISM2_HOSTAPD_SET_RATE_SETS.
>>>       
>> I don't think I would like to get this applied since this seems to be
>> changing the design on how the per-STA TX rate limiting is done in a
>> way that does not match the original design and no justification has
>> been given for that change so far. Some comments below.
>>     
>
> I agree with Jouni. We definitely want similar feature but it needs to be
> carefully designed (and no, we are not limited by the limitations of WE).
> I'm not going to apply the patch.
>
>  Jiri
>
>   
I can not see how does it break per-STA TX rate limit, especially 
PRISM2_HOSTAPD_SET_RATE_SETS almost doing the same thing. I am not saying
the patch is correct I just want to know how to fix it to get it in.
Mohamed

  reply	other threads:[~2006-09-21 17:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-28 20:45 [PATCH 2/7] d80211: add support for SIOCSIWRATE and SIOCGIWRATE mabbas
2006-08-30 17:19 ` Jouni Malinen
2006-08-30 18:23   ` Mohamed Abbas
2006-09-21 16:40   ` Jiri Benc
2006-09-21 16:59     ` mabbas [this message]
2006-09-28 11:38       ` Jiri Benc
2006-10-12 22:35         ` mabbas
2006-10-18 12:59           ` Jiri Benc
2006-10-18 13:02             ` Johannes Berg
2006-10-18 13:34               ` Jiri Benc
2006-10-18 13:42                 ` 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=4512C4FB.5010704@linux.intel.com \
    --to=mabbas@linux.intel.com \
    --cc=jbenc@suse.cz \
    --cc=jkm@devicescape.com \
    --cc=netdev@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 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.