From: Michael Buesch <mb@bu3sch.de>
To: "Simon Barber" <simon@devicescape.com>
Cc: "Jiri Benc" <jbenc@suse.cz>,
linville@tuxdriver.com, netdev@vger.kernel.org
Subject: Re: [PATCH] d80211: add ieee80211_stop_queues()
Date: Wed, 23 Aug 2006 22:20:06 +0200 [thread overview]
Message-ID: <200608232220.07093.mb@bu3sch.de> (raw)
In-Reply-To: <C86180A8C204554D8A3323D8F6B0A29F0165B5DC@dhost002-46.dex002.intermedia.net>
On Wednesday 23 August 2006 22:10, Simon Barber wrote:
> The DMA ring forms a queue of frames. Frames live in that queue for some
> time before they are transmitted. This is a source of latency between
> the software process that puts the frames in the queue and the point in
> time when they are actually transmitted.
Yes, sure. But I don't see how shortening that queue reduces
the time. Frames are always processed by the device as fast as
possible to a given "end-pointer". That end-pointer is updated
on the fly as packets come in. So if enough packets come in
the device keeps circling the ring. No matter how large it is.
The issue that we must prevent is a ring overflow by providing
a sufficiently _large_ (not small) ring. The larger the ring
the better. Theoretically an infinite ring size would be perfect,
but we don't want that for obvious memory issues. ;)
So we try to keep ring size down to a sane amount, where it's
damn unlikely to ever overflow, to reduce memory usage (and only
memory usage).
--
Greetings Michael.
next prev parent reply other threads:[~2006-08-23 20:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 11:44 [PATCH] d80211: add ieee80211_stop_queues() Michael Buesch
2006-08-23 19:30 ` Simon Barber
2006-08-23 19:45 ` Michael Buesch
2006-08-23 19:54 ` Simon Barber
2006-08-23 20:04 ` Michael Buesch
2006-08-23 20:10 ` Simon Barber
2006-08-23 20:20 ` Michael Buesch [this message]
2006-08-23 20:32 ` Simon Barber
2006-08-23 20:57 ` Michael Buesch
2006-08-23 21:12 ` Simon Barber
2006-08-23 22:07 ` Michael Buesch
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=200608232220.07093.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=simon@devicescape.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).