[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141204142015.GR27416@gospo.rtplab.test>
Date: Thu, 4 Dec 2014 09:20:15 -0500
From: Andy Gospodarek <gospo@...ulusnetworks.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net, nhorman@...driver.com,
andy@...yhouse.net, tgraf@...g.ch, dborkman@...hat.com,
ogerlitz@...lanox.com, jesse@...ira.com, pshelar@...ira.com,
azhou@...ira.com, ben@...adent.org.uk, stephen@...workplumber.org,
jeffrey.t.kirsher@...el.com, vyasevic@...hat.com,
xiyou.wangcong@...il.com, john.r.fastabend@...el.com,
edumazet@...gle.com, jhs@...atatu.com, sfeldma@...il.com,
f.fainelli@...il.com, roopa@...ulusnetworks.com,
linville@...driver.com, jasowang@...hat.com, ebiederm@...ssion.com,
nicolas.dichtel@...nd.com, ryazanov.s.a@...il.com,
buytenh@...tstofly.org, aviadr@...lanox.com, nbd@...nwrt.org,
alexei.starovoitov@...il.com, Neil.Jerram@...aswitch.com,
ronye@...lanox.com, simon.horman@...ronome.com,
alexander.h.duyck@...hat.com, john.ronciak@...el.com,
mleitner@...hat.com, shrijeet@...il.com, bcrl@...ck.org,
hemal@...adcom.com
Subject: Re: [patch iproute2 1/6] iproute2: ipa: show switch id
On Thu, Dec 04, 2014 at 09:57:13AM +0100, Jiri Pirko wrote:
> Signed-off-by: Jiri Pirko <jiri@...nulli.us>
> ---
> include/linux/if_link.h | 1 +
> ip/ipaddress.c | 8 ++++++++
> 2 files changed, 9 insertions(+)
>
> diff --git a/include/linux/if_link.h b/include/linux/if_link.h
> index 4732063..a6e2594 100644
> --- a/include/linux/if_link.h
> +++ b/include/linux/if_link.h
> @@ -145,6 +145,7 @@ enum {
> IFLA_CARRIER,
> IFLA_PHYS_PORT_ID,
> IFLA_CARRIER_CHANGES,
> + IFLA_PHYS_SWITCH_ID,
Serious question for Stephen et al, once we take this to iproute2 are we
going to be able to change the name but the string diplayed if needed?
I had a patch that called this IFLA_PARENT_ID that I was using with the
older github tree used by Jiri and Scott before these were in net-next.
I wanted to submit that as a change to what became
82f2841291cfaf4d225aa1766424280254d3e3b2, but was waiting for things to
be accepted and the dust settled.
I like the parent/child/sibling nomenclature better for 4 reasons:
- Most did not seem to like the term 'offload' since that term would be
confusing with, GRO, GSO, etc.
- A *significant* use case for many of the high-end ASICs in datacenters
is routing.
- switchid does not make sense in the OVS/flow case because it is all
about flows, not switches or routers, and parent made sense there.
- I wanted to combine this for use with SR-IOV use case, so one can more
easily map PF->VF using this.
Can you give me a bit (a day) to clean-up that patch and submit an
alternative proposal to these?
> __IFLA_MAX
> };
>
> diff --git a/ip/ipaddress.c b/ip/ipaddress.c
> index 4d99324..bd36a07 100644
> --- a/ip/ipaddress.c
> +++ b/ip/ipaddress.c
> @@ -589,6 +589,14 @@ int print_linkinfo(const struct sockaddr_nl *who,
> b1, sizeof(b1)));
> }
>
> + if (tb[IFLA_PHYS_SWITCH_ID]) {
> + SPRINT_BUF(b1);
> + fprintf(fp, "switchid %s ",
> + hexstring_n2a(RTA_DATA(tb[IFLA_PHYS_SWITCH_ID]),
> + RTA_PAYLOAD(tb[IFLA_PHYS_SWITCH_ID]),
> + b1, sizeof(b1)));
> + }
> +
> if (tb[IFLA_OPERSTATE])
> print_operstate(fp, rta_getattr_u8(tb[IFLA_OPERSTATE]));
>
> --
> 1.9.3
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists