From: Or Gerlitz <or.gerlitz@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
stephen@networkplumber.org, Narendra_K@dell.com,
bhutchings@solarflare.com, john.r.fastabend@intel.com
Subject: Re: [patch net-next v3 1/3] net: add ndo to get id of physical port of the device
Date: Mon, 22 Jul 2013 18:59:37 +0300 [thread overview]
Message-ID: <CAJZOPZ+tbr8qvCJ7wDbXUhOEh4Q6j-_J1CFzFkb8nm4e3AwSrA@mail.gmail.com> (raw)
In-Reply-To: <1374498317-6442-2-git-send-email-jiri@resnulli.us>
On Mon, Jul 22, 2013 at 4:05 PM, Jiri Pirko <jiri@resnulli.us> wrote:
> This patch adds a ndo for getting physical port of the device. Driver
> which is aware of being virtual function of some physical port should
> implement this ndo. This is applicable not only for IOV, but for other
> solutions (NPAR, multichannel) as well. Basically if there is possible
> to have multiple netdevs on the single hw port.
BTW - one thing which can be helpful for the discussion, is to have
this new ndo actually implemented for a certain driver. Also typically
we prefer to avoid adding new features at the networking core layer
without any concrete user. Making some driver to implement a new
feature is always a good way to see it flies well.
Or.
>
> Signed-off-by: Jiri Pirko <jiri@resnulli.us>
> Acked-by: Ben Hutchings <bhutchings@solarflare.com>
next prev parent reply other threads:[~2013-07-22 15:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-22 13:05 [patch net-next v3 0/3] export device physical port id to userspace Jiri Pirko
2013-07-22 13:05 ` [patch net-next v3 1/3] net: add ndo to get id of physical port of the device Jiri Pirko
2013-07-22 13:44 ` Narendra_K
2013-07-22 15:59 ` Or Gerlitz [this message]
2013-07-22 18:01 ` Jiri Pirko
2013-07-22 18:37 ` Or Gerlitz
2013-07-22 13:05 ` [patch net-next v3 2/3] rtnl: export physical port id via RT netlink Jiri Pirko
2013-07-22 13:05 ` [patch net-next v3 3/3] net: export physical port id via sysfs Jiri Pirko
2013-07-24 23:01 ` David Miller
2013-07-24 23:00 ` [patch net-next v3 0/3] export device physical port id to userspace David Miller
2013-07-25 7:41 ` Jiri Pirko
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=CAJZOPZ+tbr8qvCJ7wDbXUhOEh4Q6j-_J1CFzFkb8nm4e3AwSrA@mail.gmail.com \
--to=or.gerlitz@gmail.com \
--cc=Narendra_K@dell.com \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=jiri@resnulli.us \
--cc=john.r.fastabend@intel.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).