Netdev List
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: sunil.kovvuri@gmail.com, netdev@vger.kernel.org,
	davem@davemloft.net, leon@kernel.org,
	Tomasz Duszynski <tduszynski@marvell.com>,
	Sunil Goutham <sgoutham@marvell.com>
Subject: Re: [PATCH v3 net-next 4/8] octeontx2-vf: Ethtool support
Date: Thu, 19 Mar 2020 15:42:11 -0700	[thread overview]
Message-ID: <20200319154211.4bf7cf01@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <20200319155631.GC27807@lunn.ch>

On Thu, 19 Mar 2020 16:56:31 +0100 Andrew Lunn wrote:
> On Thu, Mar 19, 2020 at 06:37:24PM +0530, sunil.kovvuri@gmail.com wrote:
> > From: Tomasz Duszynski <tduszynski@marvell.com>
> > 
> > Added ethtool support for VF devices for
> >  - Driver stats, Tx/Rx perqueue stats
> >  - Set/show Rx/Tx queue count
> >  - Set/show Rx/Tx ring sizes
> >  - Set/show IRQ coalescing parameters
> >  - RSS configuration etc
> > 
> > It's the PF which owns the interface, hence VF
> > cannot display underlying CGX interface stats.
> > Except for this rest ethtool support reuses PF's
> > APIs.
> > 
> > Signed-off-by: Tomasz Duszynski <tduszynski@marvell.com>
> > Signed-off-by: Sunil Goutham <sgoutham@marvell.com>  
> 
> Reviewed-by: Andrew Lunn <andrew@lunn.ch>

But they didn't add static inlines, no? Don't the dependencies 
look strange?

VF depends on PF code, but ethtool code (part of PF) also needs 
symbols from the VF..

Are the kconfig options really needed? If the dependencies are
circular, this will either not work well or have all the modules 
loaded together. So let's just have everything under one kconfig 
knob and not bother breaking it up at module boundaries..

Note that it's perfectly fine to have multiple drivers in one module
(it used to be harder long time ago).

  reply	other threads:[~2020-03-19 22:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-19 13:07 [PATCH v3 net-next 0/8] octeontx2-vf: Add network driver for virtual function sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 1/8] octeontx2-pf: Enable SRIOV and added VF mbox handling sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 2/8] octeontx2-pf: Handle VF function level reset sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 3/8] octeontx2-vf: Virtual function driver support sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 4/8] octeontx2-vf: Ethtool support sunil.kovvuri
2020-03-19 15:56   ` Andrew Lunn
2020-03-19 22:42     ` Jakub Kicinski [this message]
2020-03-20  7:05       ` Sunil Kovvuri
2020-03-20 17:14         ` Jakub Kicinski
2020-03-19 13:07 ` [PATCH v3 net-next 5/8] octeontx2-vf: Link event notification support sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 6/8] octeontx2-pf: Cleanup all receive buffers in SG descriptor sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 7/8] octeontx2-af: Remove driver version and fix authorship sunil.kovvuri
2020-03-19 13:07 ` [PATCH v3 net-next 8/8] octeontx2-pf: Remove wrapper APIs for mutex lock and unlock sunil.kovvuri

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=20200319154211.4bf7cf01@kicinski-fedora-PC1C0HJN \
    --to=kuba@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=leon@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=sgoutham@marvell.com \
    --cc=sunil.kovvuri@gmail.com \
    --cc=tduszynski@marvell.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