From: Eric Dumazet <eric.dumazet@gmail.com>
To: Kumar Gopalpet-B05799 <B05799@freescale.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: [RFC] gianfar: multi queue stuff not complete
Date: Thu, 19 Nov 2009 10:13:09 +0100 [thread overview]
Message-ID: <4B050C25.5010309@gmail.com> (raw)
In-Reply-To: <9F4C7D19E8361D4C94921B95BE08B81B950E25@zin33exm22.fsl.freescale.net>
Kumar Gopalpet-B05799 a écrit :
>
> Eric, Yes I agree that still there are a couple of changes left and I am
> working on it.
> One of them being the stats. Currently caught up in something else, I
> will update them ASAP.
>
> Also, suggest me on what kind of stats do I need to maintain ? Both per
> device and per queue
> or only per queue would be sufficient ?
>
Optimum would be per queue only, to avoid locking and let each queue be really independant.
next prev parent reply other threads:[~2009-11-19 9:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-19 8:28 [RFC] gianfar: multi queue stuff not complete Eric Dumazet
2009-11-19 8:52 ` Kumar Gopalpet-B05799
2009-11-19 9:13 ` Eric Dumazet [this message]
2009-11-19 9:14 ` Kumar Gopalpet-B05799
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=4B050C25.5010309@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=B05799@freescale.com \
--cc=davem@davemloft.net \
--cc=netdev@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).