On Sun Sep 25 2022, Richard Cochran wrote:
> On Mon, Sep 05, 2022 at 04:35:58PM +0200, Kurt Kanzenbach wrote:
>> Yes, this should work. Thanks!
>
> Kurt,
>
> Does this mean you can use the dscp_ settings, and the new
> "socket_priority" from your patch isn't needed?
Hi Richard,
well, allowing to
On Mon, Sep 05, 2022 at 04:35:58PM +0200, Kurt Kanzenbach wrote:
> Yes, this should work. Thanks!
Kurt,
Does this mean you can use the dscp_ settings, and the new
"socket_priority" from your patch isn't needed?
Thanks,
Richard
___
Linuxptp-devel ma
On Wed Aug 31 2022, Vinicius Costa Gomes wrote:
> Richard Cochran writes:
>
>> On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
>>> ptp4l supports setting of socket priority. This is useful for traffic
>>> shaping
>>> e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLA
Richard Cochran writes:
> On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
>> ptp4l supports setting of socket priority. This is useful for traffic shaping
>> e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLAN egress
>> mappings.
>
> Why can't Qdisc use the dialed ds
On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
> ptp4l supports setting of socket priority. This is useful for traffic shaping
> e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLAN egress
> mappings.
Why can't Qdisc use the dialed dscp_event and dscp_general settings
On Tue Aug 30 2022, Erez wrote:
>> There already are two sockets. One for event messages and another for
>> everything else. A (multicast) PTP server sends event messages at a
>> constant rate. The rate of other messages depends on the number of
>> clients and rate of their requests.
>>
>
> Yet I s
On Tue, 30 Aug 2022 at 12:52, Miroslav Lichvar wrote:
> On Tue, Aug 30, 2022 at 12:43:24PM +0200, Erez wrote:
> > On Tue, 30 Aug 2022 at 12:28, Miroslav Lichvar
> wrote:
> >
> > > On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
> > > > ptp4l supports setting of socket priority.
On Tue, Aug 30, 2022 at 12:43:24PM +0200, Erez wrote:
> On Tue, 30 Aug 2022 at 12:28, Miroslav Lichvar wrote:
>
> > On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
> > > ptp4l supports setting of socket priority. This is useful for traffic
> > shaping
> > > e.g., utilizing Tx ste
On Tue, Aug 30, 2022 at 12:42:03PM +0200, Kurt Kanzenbach wrote:
> On Tue Aug 30 2022, Miroslav Lichvar wrote:
> > Is it useful to set the priority for non-event messages? Their timing
> > is not so important and there can be a lot of traffic generated
> > remotely (e.g. management messages).
>
>
On Tue, 30 Aug 2022 at 12:28, Miroslav Lichvar wrote:
> On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
> > ptp4l supports setting of socket priority. This is useful for traffic
> shaping
> > e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLAN egress
> > mappings.
>
On Tue Aug 30 2022, Miroslav Lichvar wrote:
>> @@ -196,6 +196,19 @@ static int udp_open(struct transport *t, struct
>> interface *iface,
>> pr_warning("Failed to set general DSCP priority.");
>> }
>>
>> +socket_priority = config_get_int(t->cfg, "global", "socket_priority");
On Tue, Aug 30, 2022 at 09:30:33AM +0200, Kurt Kanzenbach wrote:
> ptp4l supports setting of socket priority. This is useful for traffic shaping
> e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLAN egress
> mappings.
>
> However, that's only implemented for Layer 2 transport. Extend
ptp4l supports setting of socket priority. This is useful for traffic shaping
e.g., utilizing Tx steering using TAPRIO or mqprio Qdisc or VLAN egress
mappings.
However, that's only implemented for Layer 2 transport. Extend this for UDPv4
and UDPv6 transports. Update the man page accordingly.
Note
13 matches
Mail list logo
