From: Stephen Hemminger <shemminger@vyatta.com>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Ben Hutchings <bhutchings@solarflare.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
xen-devel <xen-devel@lists.xensource.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Francois Romieu <romieu@fr.zoreil.com>
Subject: Re: [GIT/PATCH v4] xen network backend driver
Date: Fri, 11 Mar 2011 09:24:03 -0800 [thread overview]
Message-ID: <20110311092403.3aaca41c@nehalam> (raw)
In-Reply-To: <1299838975.17339.1882.camel@zakaz.uk.xensource.com>
On Fri, 11 Mar 2011 10:22:55 +0000
Ian Campbell <Ian.Campbell@eu.citrix.com> wrote:
> On Thu, 2011-03-10 at 17:30 +0000, Ben Hutchings wrote:
> > On Thu, 2011-03-10 at 09:15 -0800, Stephen Hemminger wrote:
> > > On Thu, 10 Mar 2011 17:02:33 +0000
> > > Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > > > +struct xenvif {
> > > > + /* Unique identifier for this interface. */
> > > ...
> > > > + struct net_device_stats stats;
> > > > +
> > >
> > > There is already a stats struct in net_device in current kernel
> > > versions, unless there is a compelling reason otherwise
> > > please use that.
>
> Will do.
>
> > > Also, you probably want to implement per-cpu and 64 bit
> > > stats.
> >
> > The driver is using a single queue, so I don't see what benefit it would
> > get from per-cpu stats. At some point it should become multiqueue and
> > then it should store per-queue stats.
>
> Agreed.
>
> > 64-bit stats are definitely preferable, but since they're being
> > maintained on the data path this may require some significant work.
> > (Ian: see <linux/u64_stats_sync.h> for the canonical way to do this.)
> > Given that only a relatively few existing drivers do this (I count 13),
> > I'm not sure we can reasonably demand that a new driver does - yet.
>
> Is there an example of a driver which also updates the stats on the
> datapath?
>
> If it's ok I'd prefer to defer this change for now though.
Sure, my original comment was just a hint for future.
--
next prev parent reply other threads:[~2011-03-11 17:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 17:02 [SPAM] [GIT/PATCH v4] xen network backend driver Ian Campbell
2011-03-10 17:14 ` Stephen Hemminger
2011-03-10 17:17 ` Ben Hutchings
2011-03-11 10:30 ` Ian Campbell
2011-03-10 17:15 ` Stephen Hemminger
2011-03-10 17:30 ` Ben Hutchings
2011-03-11 10:22 ` Ian Campbell
2011-03-11 17:24 ` Stephen Hemminger [this message]
2011-03-10 17:33 ` Michał Mirosław
2011-03-10 17:43 ` [PoC PATCH] net: convert xen-netfront to hw_features Michał Mirosław, Michał Mirosław
2011-03-10 17:47 ` [PATCH] net: convert xen-netfront to hw_features, " Michał Mirosław
2011-03-14 13:43 ` [GIT/PATCH v4] xen network backend driver Ian Campbell
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=20110311092403.3aaca41c@nehalam \
--to=shemminger@vyatta.com \
--cc=Ian.Campbell@eu.citrix.com \
--cc=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.com \
--cc=xen-devel@lists.xensource.com \
/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).