From: David Miller <davem@davemloft.net>
To: sjur.brandeland@stericsson.com
Cc: netdev@vger.kernel.org, alexey.orishko@stericsson.com,
eric.dumazet@gmail.com
Subject: Re: [PATCHv3 net-next 3/4] caif: Add support for flow-control on device's tx-queue
Date: Mon, 05 Dec 2011 18:46:19 -0500 (EST) [thread overview]
Message-ID: <20111205.184619.2049555377796266031.davem@davemloft.net> (raw)
In-Reply-To: <1323033775-3496-3-git-send-email-sjur.brandeland@stericsson.com>
From: Sjur Brændeland <sjur.brandeland@stericsson.com>
Date: Sun, 4 Dec 2011 22:22:54 +0100
> Flow control is implemented by inspecting the qdisc queue length
> in order to detect potential overflow on the TX queue. When a threshold
> is reached flow-off is sent upwards in the CAIF stack. At the same time
> the skb->destructor is hi-jacked by orphaning the SKB and the original
> destructor is replaced with a "flow-on" callback. When the "hi-jacked"
> SKB is consumed the queue should be empty, and the "flow-on" callback
> is called and xon is sent upwards in the CAIF stack.
>
> Signed-off-by: Sjur Brændeland <sjur.brandeland@stericsson.com>
Applied.
next prev parent reply other threads:[~2011-12-05 23:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-04 21:22 [PATCHv3 net-next 1/4] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1 Sjur Brændeland
2011-12-04 21:22 ` [PATCHv3 net-next 2/4] caif: Add support for CAIF over CDC NCM USB interface Sjur Brændeland
2011-12-05 23:46 ` David Miller
2011-12-04 21:22 ` [PATCHv3 net-next 3/4] caif: Add support for flow-control on device's tx-queue Sjur Brændeland
2011-12-05 23:46 ` David Miller [this message]
2011-12-04 21:22 ` [PATCHv3 net-next 4/4] caif: Stash away hijacked skb destructor and call it later Sjur Brændeland
2011-12-05 23:46 ` David Miller
2011-12-05 23:46 ` [PATCHv3 net-next 1/4] if_ether.h: Add IEEE 802.1 Local Experimental Ethertype 1 David Miller
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=20111205.184619.2049555377796266031.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexey.orishko@stericsson.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sjur.brandeland@stericsson.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).