From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Mauro Carvalho Chehab <mchehab@redhat.com>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: [PATCH RFCv9 1/4] dvb: Add DVBv5 stats properties for Quality of Service
Date: Tue, 8 Jan 2013 10:33:08 -0200 [thread overview]
Message-ID: <20130108103308.47562c31@redhat.com> (raw)
In-Reply-To: <1357604750-772-2-git-send-email-mchehab@redhat.com>
Em Mon, 7 Jan 2013 22:25:47 -0200
Mauro Carvalho Chehab <mchehab@redhat.com> escreveu:
> The DVBv3 quality parameters are limited on several ways:
>
> - Doesn't provide any way to indicate the used measure,
> so userspace need to guess how to calculate the measure;
>
> - Only a limited set of stats are supported;
>
> - Can't be called in a way to require them to be filled
> all at once (atomic reads from the hardware), with may
> cause troubles on interpreting them on userspace;
>
> - On some OFDM delivery systems, the carriers can be
> independently modulated, having different properties.
> Currently, there's no way to report per-layer stats.
>
> To address the above issues, adding a new DVBv5-based stats
> API.
>
> Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
>
...
> +struct dtv_stats {
> + __u8 scale; /* enum fecap_scale_params type */
> + union {
> + __u32 uvalue; /* for counters and relative scales */
> + __s32 svalue; /* for 0.1 dB measures */
32 bits for total bit count is not enough, as it can be truncated too
early (~1 seg on ISDB-T, ~0.5 seg on DVB-C). I think we need to use
64 bits here, and put at the API that the drivers should monotonically
increment.
As struct buffer inside struct dtv_property has 48 bytes, we can do such
change here without breaking userspace, as struct dtv_stats will have
37 bytes.
--
Cheers,
Mauro
next prev parent reply other threads:[~2013-01-08 12:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 0:25 [PATCH RFCv9 0/4] DVB QoS statistics API Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 1/4] dvb: Add DVBv5 stats properties for Quality of Service Mauro Carvalho Chehab
2013-01-08 11:45 ` Simon Farnsworth
2013-01-08 18:00 ` Frank Schäfer
2013-01-08 23:18 ` Simon Farnsworth
2013-01-08 23:28 ` Devin Heitmueller
2013-01-09 11:02 ` Simon Farnsworth
2013-01-09 15:24 ` Mauro Carvalho Chehab
2013-01-10 10:19 ` Simon Farnsworth
2013-01-13 13:30 ` [linux-media] " Klaus Schmidinger
2013-01-08 12:33 ` Mauro Carvalho Chehab [this message]
2013-01-08 0:25 ` [PATCH RFCv9 2/4] dvb: the core logic to handle the DVBv5 QoS properties Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 3/4] mb86a20s: provide signal strength via DVBv5 stats API Mauro Carvalho Chehab
2013-01-08 0:25 ` [PATCH RFCv9 4/4] mb86a20s: add BER measure Mauro Carvalho Chehab
2013-01-08 0:37 ` [PATCH RFCv9] " Mauro Carvalho Chehab
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=20130108103308.47562c31@redhat.com \
--to=mchehab@redhat.com \
--cc=linux-media@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 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).