From: Johannes Berg <johannes@sipsolutions.net>
To: vjakkam@codeaurora.org
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH] nl80211: Indicate SA Query procedures offload for AP SME device
Date: Mon, 25 Oct 2021 10:28:34 +0200 [thread overview]
Message-ID: <1dd3525ee437ff2ccf18b455851692338af342fa.camel@sipsolutions.net> (raw)
In-Reply-To: <7c5b87329c58ac2b68329573f587f8d7@codeaurora.org>
On Mon, 2021-10-25 at 13:57 +0530, vjakkam@codeaurora.org wrote:
> On 2021-10-22 18:59, Johannes Berg wrote:
> > On Fri, 2021-10-22 at 18:56 +0530, vjakkam@codeaurora.org wrote:
> > > >
> > > > So how's that going to work with older hostapd? It'll be offloaded, and
> > > > then hostapd doesn't know, so it's still going to disconnect them?
> > > >
> > > > So should be that hostapd also opts in to this driver behaviour?
> > >
> > > yes, we have to update hostapd also with new implementation based on
> > > the
> > > feature flag.
> >
> > That wasn't my question. My question was what happens if you have a
> > hostapd that's *not* updated?>
> >
> > johannes
>
> Apologies for not clear answer in my previous reply.
> Yes, If hostapd is not updated, it's going to disconnect the STAs.
>
> We should update hostapd also to opt in this driver behavior.
That would also mean the driver opts in and asks the firmware to offload
only if hostapd did, right?
johannes
next prev parent reply other threads:[~2021-10-25 8:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 11:18 [PATCH] nl80211: Indicate SA Query procedures offload for AP SME device Veerendranath Jakkam
2021-10-21 15:32 ` Johannes Berg
2021-10-22 13:26 ` vjakkam
2021-10-22 13:29 ` Johannes Berg
2021-10-25 8:27 ` vjakkam
2021-10-25 8:28 ` Johannes Berg [this message]
2021-11-22 6:11 ` vjakkam
2021-11-26 7:25 ` [PATCH 1/2] nl80211: Add support to set AP settings flags with single attribute Veerendranath Jakkam
2021-11-26 7:25 ` [PATCH 2/2] nl80211: Add support to offload SA Query procedures for AP SME device Veerendranath Jakkam
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=1dd3525ee437ff2ccf18b455851692338af342fa.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=vjakkam@codeaurora.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;
as well as URLs for NNTP newsgroup(s).