From: Edward Cree <ecree.xilinx@gmail.com>
To: "Íñigo Huguet" <ihuguet@redhat.com>,
habetsm.xilinx@gmail.com, richardcochran@gmail.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, netdev@vger.kernel.org,
Yalin Li <yalli@redhat.com>
Subject: Re: [PATCH RESEND net-next v4 4/4] sfc: remove expired unicast PTP filters
Date: Wed, 15 Mar 2023 16:17:13 +0000 [thread overview]
Message-ID: <70906786-d2c3-652f-84a1-2f6dcddf00f3@gmail.com> (raw)
In-Reply-To: <a2d55af3-df0c-2ed8-fc2c-78c0da6e6390@redhat.com>
On 15/03/2023 08:54, Íñigo Huguet wrote:
>> PTP worker runs on every PTP packet TX or RX, which might be
>> quite frequent. It's probably fine but do we need to consider
>> limiting how much time we spend repeatedly scanning the list?
>
> PTP traffic is not that frequent, few packets per second, isn't it?
>
>> Conversely, if all PTP traffic suddenly stops, I think existing
>> unicast filters will stay indefinitely. Again probably fine
>> but just want to check that sounds sane to everyone.
>
> Yes, it's as you say. However, I thought it didn't worth it to create a new periodic worker only for this, given that I expected a short list, it wouldn't be harmful. However, as I said in the other message, maybe the list can be quite long if we're the PTP master?
>
> Maybe I should create a dedicated periodic work for this? That would avoid both problems that you are pointing out.
I'm not a PTP expert, hence why my comments above were phrased as
questions rather than answers ;)
Up to you whether you think a dedicated work is needed; again, my
Ack stands as it is, I'm happy for this to be done in a followup
or not at all.
prev parent reply other threads:[~2023-03-15 16:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-14 10:09 [PATCH RESEND net-next v4 0/4] sfc: support unicast PTP Íñigo Huguet
2023-03-14 10:09 ` [PATCH RESEND net-next v4 1/4] sfc: store PTP filters in a list Íñigo Huguet
2023-03-14 16:25 ` Edward Cree
2023-03-14 10:09 ` [PATCH RESEND net-next v4 2/4] sfc: allow insertion of filters for unicast PTP Íñigo Huguet
2023-03-14 16:28 ` Edward Cree
2023-03-14 10:09 ` [PATCH RESEND net-next v4 3/4] sfc: support " Íñigo Huguet
2023-03-14 16:55 ` Edward Cree
2023-03-15 8:48 ` Íñigo Huguet
2023-03-15 16:14 ` Edward Cree
2023-03-14 10:09 ` [PATCH RESEND net-next v4 4/4] sfc: remove expired unicast PTP filters Íñigo Huguet
2023-03-14 17:24 ` Edward Cree
2023-03-15 8:54 ` Íñigo Huguet
2023-03-15 16:17 ` Edward Cree [this message]
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=70906786-d2c3-652f-84a1-2f6dcddf00f3@gmail.com \
--to=ecree.xilinx@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=habetsm.xilinx@gmail.com \
--cc=ihuguet@redhat.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=yalli@redhat.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.