From: Johannes Berg <johannes@sipsolutions.net>
To: Bing Zhao <bzhao@marvell.com>
Cc: linux-wireless@vger.kernel.org, Amitkumar Karwar <akarwar@marvell.com>
Subject: Re: [PATCH v5] cfg80211/nl80211: Add packet coalesce support
Date: Mon, 08 Jul 2013 13:15:32 +0200 [thread overview]
Message-ID: <1373282132.8312.9.camel@jlt4.sipsolutions.net> (raw)
In-Reply-To: <1372445486-10466-1-git-send-email-bzhao@marvell.com>
On Fri, 2013-06-28 at 11:51 -0700, Bing Zhao wrote:
> From: Amitkumar Karwar <akarwar@marvell.com>
>
> In most cases, host that receives IPv4 and IPv6 multicast/broadcast
> packets does not do anything with these packets. Therefore the
> reception of these unwanted packets causes unnecessary processing
> and power consumption.
>
> Packet coalesce feature helps to reduce number of received
> interrupts to host by buffering these packets in firmware/hardware
> for some predefined time. Received interrupt will be generated when
> one of the following events occur.
> a) Expiration of hardware timer whose expiration time is set to
> maximum coalescing delay of matching coalesce rule.
> b) Coalescing buffer in hardware reaches it's limit.
> c) Packet doesn't match any of the configured coalesce rules.
>
> This patch adds set/get configuration support for packet coalesce.
> User needs to configure following parameters for creating a coalesce
> rule.
> a) Maximum coalescing delay
> b) List of packet patterns which needs to be matched
> c) Condition for coalescence. pattern 'match' or 'no match'
> Multiple such rules can be created.
>
> This feature needs to be advertised during driver initialization.
> Drivers are supposed to do required firmware/hardware settings based
> on user configuration.
Applied.
johannes
prev parent reply other threads:[~2013-07-08 11:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 18:51 [PATCH v5] cfg80211/nl80211: Add packet coalesce support Bing Zhao
2013-07-08 11:15 ` Johannes Berg [this message]
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=1373282132.8312.9.camel@jlt4.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=akarwar@marvell.com \
--cc=bzhao@marvell.com \
--cc=linux-wireless@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).