From: Valdis.Kletnieks@vt.edu (Valdis.Kletnieks at vt.edu)
To: kernelnewbies@lists.kernelnewbies.org
Subject: net_device: limit rate ot tx packets
Date: Sun, 14 Apr 2013 10:35:16 -0400 [thread overview]
Message-ID: <79092.1365950116@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Sun, 14 Apr 2013 10:09:54 +0200." <20130414080954.GB2288@grml>
On Sun, 14 Apr 2013 10:09:54 +0200, michi1 at michaelblizek.twilightparadox.com said:
> This is not what I meant. When the qdisc has a size of say 256KB and the
> socket memory is, say 128kb, the socket memory limit will be reached before
> the qdisc limit and the socket will sleep. But when the socket memory limit
> is greater than the qdisc limit, it will be interesting whether the socket
> still sleeps or starts dropping packets.
How to figure this out for yourself:
Look at net/sched/sch_plug.c, which is a pretty simple qdisc (transmit packets
until a plug request is recieved, then queue until unplugged). In particular,
look at plug_enqueue() to see what happens when q->limit is exceeded, and
plug_init() to see where q->limit is set.
Then look at the definition of qdisc_reshape_fail() in
include/net/sch_generic.h to figure out what the qdisc returns if q->limit is
exceeded.
Then go look at net/core/dev.c, in function __dev_xmit_skb(), and
watch the variable 'rc'.
Now go find the caller of __dev_xmit_skb() and see what it does with
that return value.
Hope that helps...
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 865 bytes
Desc: not available
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20130414/ed588d4b/attachment.bin
next prev parent reply other threads:[~2013-04-14 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 12:11 net_device: limit rate ot tx packets christian+kn at wwad.de
2013-04-14 6:15 ` michi1 at michaelblizek.twilightparadox.com
2013-04-14 7:45 ` Valdis.Kletnieks at vt.edu
2013-04-14 8:09 ` michi1 at michaelblizek.twilightparadox.com
2013-04-14 14:35 ` Valdis.Kletnieks at vt.edu [this message]
2013-04-17 14:30 ` christian+kn at wwad.de
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=79092.1365950116@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=kernelnewbies@lists.kernelnewbies.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).