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 13:21:45 +0200 [thread overview]
Message-ID: <1433071305.2370.14.camel@sipsolutions.net> (raw)
In-Reply-To: <CABPxzY+9FwDPwRcZ4QT4QcfhMqmaQsrs=LT5E8tDKQG2t+wFRA@mail.gmail.com> (sfid-20150531_131751_864869_998A17F8)
On Sun, 2015-05-31 at 16:47 +0530, Krishna Chaitanya wrote:
> > Note # of "messages" as you say is actually irrelevant - you should look
>
> Well with 138 messages the function and each message 3072 bytes
> calls b/w cfg80211 and driver
> without the patch: would be 276 calls
> with this patch: would be 138 calls
> Thats a lot of function calls, don't you think?
No, I don't think so. That really should be within the noise, it's all
in the icache already after the first round.
> > 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.
>
> My patch doesn't deteriorate the situation, and not change the kernel to
> user boundary. With/Without the patch 3072 bytes are transported in a
> single message from kernel to user.
*in your case*
In the case that somebody is creating smaller messages it makes things
MUCH worse by allowing only half the data to be carried across the
kernel/userspace boundary each time any data crosses it, so it will
result in many more syscalls in that case. If you're worried about the
overhead of a simple function (pointer) call in the kernel, then surely
you should be far more worried about this.
johannes
next prev parent reply other threads:[~2015-05-31 11:21 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
2015-05-31 11:17 ` Krishna Chaitanya
2015-05-31 11:21 ` Johannes Berg [this message]
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=1433071305.2370.14.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.