From: Martin Schiller <ms@dev.tdt.de>
To: Xie He <xie.he.0141@gmail.com>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Linux X25 <linux-x25@vger.kernel.org>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Krzysztof Halasa <khc@pm.waw.pl>
Subject: Re: [PATCH net] net: hdlc_x25: Use qdisc to queue outgoing LAPB frames
Date: Fri, 29 Jan 2021 06:56:10 +0100 [thread overview]
Message-ID: <3f67b285671aaa4b7903733455a730e1@dev.tdt.de> (raw)
In-Reply-To: <CAJht_EOSB-m--Ombr6wLMFq4mPy8UTpsBri2CPsaRTU-aks7Uw@mail.gmail.com>
On 2021-01-28 23:06, Xie He wrote:
> On Thu, Jan 28, 2021 at 11:47 AM Jakub Kicinski <kuba@kernel.org>
> wrote:
>>
>> Noob question - could you point at or provide a quick guide to
>> layering
>> here? I take there is only one netdev, and something maintains an
>> internal queue which is not stopped when HW driver stops the qdisc?
>
> Yes, there is only one netdev. The LAPB module (net/lapb/) (which is
> used as a library by the netdev driver - hdlc_x25.c) is maintaining an
> internal queue which is not stopped when the HW driver stops the
> qdisc.
>
> The queue is "write_queue" in "struct lapb_cb" in
> "include/net/lapb.h". The code that takes skbs out of the queue and
> feeds them to lower layers for transmission is at the "lapb_kick"
> function in "net/lapb/lapb_out.c".
>
> The layering is like this:
>
> Upper layer (Layer 3) (net/x25/ or net/packet/)
>
> ^
> | L3 packets (with control info)
> v
>
> The netdev driver (hdlc_x25.c)
>
> ^
> | L3 packets
> v
>
> The LAPB Module (net/lapb/)
>
> ^
> | LAPB (L2) frames
> v
>
> The netdev driver (hdlc_x25.c)
>
> ^
> | LAPB (L2) frames
> | (also called HDLC frames in the context of the HDLC subsystem)
> v
>
> HDLC core (hdlc.c)
>
> ^
> | HDLC frames
> v
>
> HDLC Hardware Driver
@Xie: Thank you for the detailed presentation.
>
>> Sounds like we're optimizing to prevent drops, and this was not
>> reported from production, rather thru code inspection. Ergo I think
>> net-next will be more appropriate here, unless Martin disagrees.
>
> Yes, I have no problem in targeting net-next instead. Thanks!
I agree.
next prev parent reply other threads:[~2021-01-29 5:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-27 9:07 [PATCH net] net: hdlc_x25: Use qdisc to queue outgoing LAPB frames Xie He
2021-01-27 10:14 ` David Laight
2021-01-27 20:29 ` Xie He
2021-01-28 6:39 ` Martin Schiller
2021-01-28 19:46 ` Jakub Kicinski
2021-01-28 22:06 ` Xie He
2021-01-29 5:56 ` Martin Schiller [this message]
2021-01-30 1:36 ` Jakub Kicinski
2021-01-30 14:29 ` Xie He
2021-01-30 19:16 ` Jakub Kicinski
2021-01-31 3:16 ` Xie He
2021-02-01 9:18 ` Martin Schiller
2021-02-01 11:38 ` Xie He
2021-02-01 13:14 ` Martin Schiller
2021-02-01 14:02 ` Xie He
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=3f67b285671aaa4b7903733455a730e1@dev.tdt.de \
--to=ms@dev.tdt.de \
--cc=davem@davemloft.net \
--cc=khc@pm.waw.pl \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-x25@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xie.he.0141@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).