All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Zefir Kurtisi <zefir.kurtisi@neratec.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: A good way to get CSI info to user-space?
Date: Wed, 25 Oct 2017 07:43:05 -0700	[thread overview]
Message-ID: <73fbd13f-50bb-b8c1-657b-ab2cfe015dc8@candelatech.com> (raw)
In-Reply-To: <4e1f9cc5-5689-93fb-0c02-115e03268c1d@neratec.com>



On 10/25/2017 07:30 AM, Zefir Kurtisi wrote:
> Hi Ben,
>
> On 10/24/2017 03:55 PM, Johannes Berg wrote:
>> On Tue, 2017-10-24 at 06:50 -0700, Ben Greear wrote:
>> [...]
>>> Anyone know if there is a useful way to stream events from debugfs
>>> and/or sysfs w/out having to busy-poll on it?
>>
>> There's relayfs, which is kinda built for that. You could even use
>> netlink vendor events, but I don't really think netlink is appropriate
>> here.
>>
> This is what I would also suggest, alas it is not clear if the events need to be
> processed realtime.
>
> The relayfs is used to stream the spectral data from ath9k (and afaik also from
> ath10k) to userspace. Very easy to implement: kernel pushes TLVs into the relayfs,
> userspace pulls them.
>
> It is 'realtime-enough' to display realtime spectral graphs, but since you are
> reading the stream in buffer-slices, you have to wait for a slice to fill up
> before it is available at userspace (or you flush every TLV at kernel side, which
> kills efficiency).
>
> That is: if you need to immediately process events, relayfs is maybe not the right
> choice, if you can process them in bulk, that's the most efficient way to go.

The netlink vendor API seems to do exactly what I was hoping for earlier,
so I have started poking at that.

There is at least one other set of 'per-peer tx-beamforming' data that might be worth
exporting via the same mechanism.

Any particular reason why relayfs would be better than netlink?

Thanks,
Ben


-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

  reply	other threads:[~2017-10-25 14:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 17:54 A good way to get CSI info to user-space? Ben Greear
2017-10-23 20:30 ` Johannes Berg
2017-10-23 20:59   ` Ben Greear
2017-10-24  5:54     ` Johannes Berg
2017-10-24 13:36       ` Ben Greear
2017-10-24 13:38         ` Johannes Berg
2017-10-24 13:50           ` Ben Greear
2017-10-24 13:55             ` Johannes Berg
2017-10-24 20:15               ` Ben Greear
2017-10-25 14:30               ` Zefir Kurtisi
2017-10-25 14:43                 ` Ben Greear [this message]
2017-10-25 15:35                   ` Zefir Kurtisi

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=73fbd13f-50bb-b8c1-657b-ab2cfe015dc8@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=zefir.kurtisi@neratec.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 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.