From: Herve Codina <herve.codina@bootlin.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Vadim Fedorenko <vadim.fedorenko@linux.dev>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>,
Mark Brown <broonie@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Jakub Kicinski <kuba@kernel.org>,
linuxppc-dev@lists.ozlabs.org,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH v2 1/6] net: wan: Add support for QMC HDLC
Date: Mon, 5 Feb 2024 17:35:50 +0100 [thread overview]
Message-ID: <20240205173550.2a6b8f20@bootlin.com> (raw)
In-Reply-To: <d174364c12366b1f5eeb616cba078f6682d629f5.camel@redhat.com>
On Mon, 05 Feb 2024 16:49:33 +0100
Paolo Abeni <pabeni@redhat.com> wrote:
[...
> > >
> > > In general is quite bad that the existing infra does not allow
> > > leveraging NAPI. Have you considered expanding the QMC to accomodate
> > > such user?
> >
> > I cannot mask/unmask the 'end of transfer' interrupt.
> > Indeed, other streams use this interrupt among them audio streams and so
> > masking the interrupt for HDLC data will also mask the interrupt for audio
> > data.
>
> Uhm... I fear the above makes the available options list empty :(
>
> > At the HDLC driver level, the best I can to is to store a queue of complete
> > HDLC skbs (queue filled on interrupts) and send them to the network stack
> > when the napi poll() is called.
> >
> > I am not sure that this kind of queue (additional level between always
> > enabled interrupts and the network stack) makes sense.
> >
> > Do you have any opinion about this additional queue management for NAPI
> > support?
>
> With such idea in place, what HDLC-level data will be accessed by the
> napi context? The RX interrupts will remain unmasked after the
> interrupt and before the napi poll right? That would be
> problematic/could cause drop if the ingress pkt/interrupt rate will be
> higher that what the napi could process - and that in turn could bring
> back old bad livelock times :(
Indeed.
So the best thing to do is to keep this driver without NAPI support.
Best regards,
Hervé
WARNING: multiple messages have this Message-ID (diff)
From: Herve Codina <herve.codina@bootlin.com>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Vadim Fedorenko <vadim.fedorenko@linux.dev>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, Andrew Lunn <andrew@lunn.ch>,
Mark Brown <broonie@kernel.org>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [PATCH v2 1/6] net: wan: Add support for QMC HDLC
Date: Mon, 5 Feb 2024 17:35:50 +0100 [thread overview]
Message-ID: <20240205173550.2a6b8f20@bootlin.com> (raw)
In-Reply-To: <d174364c12366b1f5eeb616cba078f6682d629f5.camel@redhat.com>
On Mon, 05 Feb 2024 16:49:33 +0100
Paolo Abeni <pabeni@redhat.com> wrote:
[...
> > >
> > > In general is quite bad that the existing infra does not allow
> > > leveraging NAPI. Have you considered expanding the QMC to accomodate
> > > such user?
> >
> > I cannot mask/unmask the 'end of transfer' interrupt.
> > Indeed, other streams use this interrupt among them audio streams and so
> > masking the interrupt for HDLC data will also mask the interrupt for audio
> > data.
>
> Uhm... I fear the above makes the available options list empty :(
>
> > At the HDLC driver level, the best I can to is to store a queue of complete
> > HDLC skbs (queue filled on interrupts) and send them to the network stack
> > when the napi poll() is called.
> >
> > I am not sure that this kind of queue (additional level between always
> > enabled interrupts and the network stack) makes sense.
> >
> > Do you have any opinion about this additional queue management for NAPI
> > support?
>
> With such idea in place, what HDLC-level data will be accessed by the
> napi context? The RX interrupts will remain unmasked after the
> interrupt and before the napi poll right? That would be
> problematic/could cause drop if the ingress pkt/interrupt rate will be
> higher that what the napi could process - and that in turn could bring
> back old bad livelock times :(
Indeed.
So the best thing to do is to keep this driver without NAPI support.
Best regards,
Hervé
next prev parent reply other threads:[~2024-02-05 16:36 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-30 8:40 [PATCH v2 0/6] Add support for QMC HDLC Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 1/6] net: wan: " Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-02-01 11:41 ` Paolo Abeni
2024-02-01 11:41 ` Paolo Abeni
2024-02-05 14:22 ` Herve Codina
2024-02-05 14:22 ` Herve Codina
2024-02-05 15:49 ` Paolo Abeni
2024-02-05 15:49 ` Paolo Abeni
2024-02-05 16:35 ` Herve Codina [this message]
2024-02-05 16:35 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 2/6] MAINTAINERS: Add the Freescale QMC HDLC driver entry Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 3/6] bitmap: Make bitmap_onto() available to users Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 4/6] bitmap: Introduce bitmap_off() Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 5/6] net: wan: fsl_qmc_hdlc: Add runtime timeslots changes support Herve Codina
2024-01-30 8:40 ` Herve Codina
2024-02-01 12:01 ` Paolo Abeni
2024-02-01 12:01 ` Paolo Abeni
2024-02-05 15:00 ` Herve Codina
2024-02-05 15:00 ` Herve Codina
2024-01-30 8:40 ` [PATCH v2 6/6] net: wan: fsl_qmc_hdlc: Add framer support Herve Codina
2024-01-30 8:40 ` Herve Codina
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=20240205173550.2a6b8f20@bootlin.com \
--to=herve.codina@bootlin.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=thomas.petazzoni@bootlin.com \
--cc=vadim.fedorenko@linux.dev \
/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.