From: Kurt Kanzenbach <kurt@linutronix.de>
To: Jakub Kicinski <kuba@kernel.org>, Vladimir Oltean <olteanv@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vivien Didelot <vivien.didelot@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Vinicius Costa Gomes <vinicius.gomes@intel.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v2 net-next 1/1] net: dsa: hellcreek: Add TAPRIO offloading support
Date: Wed, 20 Jan 2021 08:18:15 +0100 [thread overview]
Message-ID: <87turc2i14.fsf@kurt> (raw)
In-Reply-To: <20210119155703.7064800d@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
[-- Attachment #1: Type: text/plain, Size: 1506 bytes --]
On Tue Jan 19 2021, Jakub Kicinski wrote:
> On Sat, 16 Jan 2021 13:49:22 +0100 Kurt Kanzenbach wrote:
>> + if (base_time_ns - current_ns < (s64)8 * NSEC_PER_SEC)
>> + return true;
>> +
>> + return false;
>
> nit:
> return base_time_ns - current_ns < (s64)8 * NSEC_PER_SEC;
Sure.
>> + /* Schedule periodic schedule check */
>> + schedule_delayed_work(&hellcreek_port->schedule_work,
>> + HELLCREEK_SCHEDULE_PERIOD);
>
> Why schedule this work every 2 seconds rather than scheduling it
> $start_time - 8 sec + epsilon?
The two seconds are taken from the programming guide. That's why I used
it.
The PTP frequency starts to matter for large deltas. In theory the
rescheduling period can be increased [1]. Should I adjust it?
>
>> +static bool hellcreek_validate_schedule(struct hellcreek *hellcreek,
>> + struct tc_taprio_qopt_offload *schedule)
>> +{
>> + /* Does this hellcreek version support Qbv in hardware? */
>> + if (!hellcreek->pdata->qbv_support)
>> + return false;
>> +
>> + /* cycle time can only be 32bit */
>> + if (schedule->cycle_time > (u32)-1)
>> + return false;
>> +
>> + /* cycle time extension is not supported */
>> + if (schedule->cycle_time_extension)
>> + return false;
>
> What's the story with entries[i].command? I see most drivers validate
> the command is what they expect.
>
Good catch! I'll add the validation.
Thanks,
Kurt
[1] - https://lkml.kernel.org/netdev/20200901144755.jd2wnmweywwvkwvl@skbuf/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2021-01-20 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-16 12:49 [PATCH v2 net-next 0/1] net: dsa: hellcreek: Add TAPRIO offloading Kurt Kanzenbach
2021-01-16 12:49 ` [PATCH v2 net-next 1/1] net: dsa: hellcreek: Add TAPRIO offloading support Kurt Kanzenbach
2021-01-17 21:21 ` Vladimir Oltean
2021-01-19 23:57 ` Jakub Kicinski
2021-01-20 7:18 ` Kurt Kanzenbach [this message]
2021-01-21 0:50 ` Jakub Kicinski
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=87turc2i14.fsf@kurt \
--to=kurt@linutronix.de \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=vinicius.gomes@intel.com \
--cc=vivien.didelot@gmail.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 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).