From: David Woodhouse <dwmw2@infradead.org>
To: Krzysztof Mazur <krzysiek@podlesie.net>
Cc: netdev@vger.kernel.org, "John Crispin" <blogic@openwrt.org>,
"Dave Täht" <dave.taht@gmail.com>,
"Chas Williams (CONTRACTOR)" <chas@cmf.nrl.navy.mil>
Subject: Re: [PATCH] atm: br2684: Fix excessive queue bloat
Date: Sun, 25 Nov 2012 22:01:32 +0000 [thread overview]
Message-ID: <1353880892.26346.300.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20121125214332.GA2722@shrek.podlesie.net>
[-- Attachment #1: Type: text/plain, Size: 1193 bytes --]
On Sun, 2012-11-25 at 22:43 +0100, Krzysztof Mazur wrote:
> On Sat, Nov 24, 2012 at 12:01:32AM +0000, David Woodhouse wrote:
> > There's really no excuse for an additional wmem_default of buffering
> > between the netdev queue and the ATM device. Two packets (one in-flight,
> > and one ready to send) ought to be fine. It's not as if it should take
> > long to get another from the netdev queue when we need it.
> >
> > If necessary we can make the queue space configurable later, but I don't
> > think it's likely to be necessary.
>
> Maybe some high-speed devices will require larger queue, especially for
> smaller packets, but 2 packet queue should be sufficient in almost all cases.
Yeah. This is fairly much the same conversation I ended up having when I
did the same for PPPoATM.
Some day *perhaps* we might look at doing something adaptive, so it'll
detect a TX underrun and increase the amount of buffering. But this
seems perfectly good for now.
> Maybe this magic "2" and the comment should be moved to some #define.
Doesn't make it any less magic. I'm happier with it as it is, with a
clear comment describing why it's done that way.
--
dwmw2
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 6171 bytes --]
next prev parent reply other threads:[~2012-11-25 22:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-24 0:01 [PATCH] atm: br2684: Fix excessive queue bloat David Woodhouse
2012-11-25 21:09 ` David Miller
2012-11-25 21:43 ` Krzysztof Mazur
2012-11-25 22:01 ` David Woodhouse [this message]
2012-11-25 23:52 ` Krzysztof Mazur
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=1353880892.26346.300.camel@shinybook.infradead.org \
--to=dwmw2@infradead.org \
--cc=blogic@openwrt.org \
--cc=chas@cmf.nrl.navy.mil \
--cc=dave.taht@gmail.com \
--cc=krzysiek@podlesie.net \
--cc=netdev@vger.kernel.org \
/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).