From: "Michał Nazarewicz" <m.nazarewicz@samsung.com>
To: David Miller <davem@davemloft.net>
Cc: dbrownell@users.sourceforge.net, gregkh@suse.de,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
eric.dumazet@gmail.com
Subject: Re: [PATCH] usb: gadget: rndis: don't use dev_get_stats()
Date: Mon, 20 Sep 2010 20:58:13 +0200 [thread overview]
Message-ID: <op.vjchnbf87p4s8u@pikus> (raw)
In-Reply-To: <20100920.112727.214208208.davem@davemloft.net>
> From: Michal Nazarewicz <m.nazarewicz@samsung.com>
>> This commit removes the call to dev_get_stats() from the
>> gen_ndis_query_resp() function. Since spin_lock_bh() was
>> added to dev_txq_stats_fold() the call started causing
>> warnings. This is because gen_ndis_query_resp() can be
>> (indirectly) called from rndis_command_complete() which is
>> called with interrupts disabled.
On Mon, 20 Sep 2010 20:27:27 +0200, David Miller <davem@davemloft.net> wrote:
> The way this works is dev_get_stats() takes that "temp" object the
> caller provides, it writes the correct statistics into it (with any
> necessary translations), and then passes back a pointer to it.
>
> See net/core/dev.c:dev_get_stats()
>
> You must use dev_get_stats() or else the statistics won't be properly
> converted.
I'm only wondering whether it's required for RNDIS to use dev_get_stats().
I haven't found reference to netdev_queue in g_ether related code and
I noticed that u_ether.c seems to update dev->stats directly.
--
Best regards, _ _
| Humble Liege of Serenely Enlightened Majesty of o' \,=./ `o
| Computer Science, Michał "mina86" Nazarewicz (o o)
+----[mina86*mina86.com]---[mina86*jabber.org]----ooO--(_)--Ooo--
prev parent reply other threads:[~2010-09-20 18:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 18:23 [PATCH] usb: gadget: rndis: don't use dev_get_stats() Michal Nazarewicz
2010-09-20 18:27 ` David Miller
2010-09-20 18:48 ` Eric Dumazet
2010-09-20 19:00 ` Michał Nazarewicz
2010-09-20 18:58 ` Michał Nazarewicz [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=op.vjchnbf87p4s8u@pikus \
--to=m.nazarewicz@samsung.com \
--cc=davem@davemloft.net \
--cc=dbrownell@users.sourceforge.net \
--cc=eric.dumazet@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@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