From: Johannes Berg <johannes@sipsolutions.net>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v2] cfg80211: Don't re-use the skb for larger NL messages.
Date: Sun, 31 May 2015 12:42:27 +0200 [thread overview]
Message-ID: <1433068947.2370.5.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzYK-8TtYdiFeFrX7AVcsXQFaa3oxHREq+jgohHh1tCg5GQ@mail.gmail.com> (sfid-20150531_120147_714239_14809F2C)
On Sun, 2015-05-31 at 15:31 +0530, Krishna Chaitanya wrote:
> In our case the data size is 411KB, and each message carries around 3072
> bytes, so total messages would be 138. The first message we get, we
> retrieve the data, and for subsequent messages we just fill the skb,
> we are not interacting with the hardware.
>
> Without this patch, heres the sequence:
> genl->cfg80211->retrieve the dump from HW, skb_put: 3072
> cfg80211->skb_put, fail
> genl->cfg80211->skb_put: 3072.
>
> With this patch:
>
> genl->cfg80211->retrive the dump from HW, skb_put: 3072
> genl->cfg80211->skb_put: 3072.
You've failed to explain why this is so much of a problem that you're
trying to "fix" it. I suspect the "fail" part inside your driver is
needlessly expensive, I don't think the function call can be expensive
enough to worry anyone.
Note # of "messages" as you say is actually irrelevant - you should look
at how often the kernel/user boundary is crossed, that's really far more
interesting, and your patch makes that MUCH worse when the put size is
small (say 100 bytes) because then you're practically doing that twice
as often.
Anyway - I stand by your patch being a terrible idea. End of story.
johannes
next prev parent reply other threads:[~2015-05-31 10:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 23:28 [PATCH v2] cfg80211: Don't re-use the skb for larger NL messages Chaitanya T K
2015-05-31 6:58 ` Arend van Spriel
2015-05-31 9:56 ` Krishna Chaitanya
2015-05-31 8:31 ` Johannes Berg
2015-05-31 10:01 ` Krishna Chaitanya
2015-05-31 10:42 ` Johannes Berg [this message]
2015-05-31 11:17 ` Krishna Chaitanya
2015-05-31 11:21 ` Johannes Berg
2015-05-31 11:39 ` Krishna Chaitanya
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=1433068947.2370.5.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=chaitanya.mgit@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.