[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZOPZJaKbMhtN4JSi6ScaRtwUNMK69trCccsdZvA7=57cDknQ@mail.gmail.com>
Date: Sun, 21 Jul 2013 14:10:41 +0300
From: Or Gerlitz <or.gerlitz@...il.com>
To: Jiri Pirko <jiri@...nulli.us>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
stephen@...workplumber.org, Narendra_K@...l.com,
bhutchings@...arflare.com, john.r.fastabend@...el.com
Subject: Re: [patch net-next v2 1/3] net: add ndo to get id of physical port
of the device
On Sat, Jul 20, 2013 at 8:53 PM, Jiri Pirko <jiri@...nulli.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.
>
> Signed-off-by: Jiri Pirko <jiri@...nulli.us>
> ---
> include/linux/netdevice.h | 20 ++++++++++++++++++++
> net/core/dev.c | 18 ++++++++++++++++++
> 2 files changed, 38 insertions(+)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 0741a1e..726dec2 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -728,6 +728,16 @@ struct netdev_fcoe_hbainfo {
> };
> #endif
>
> +#define MAX_PHYS_PORT_ID_LEN 32
> +
> +/* This structure holds a unique identifier to identify the
> + * physical port used by a netdevice.
> + */
> +struct netdev_phys_port_id {
> + unsigned char id[MAX_PHYS_PORT_ID_LEN];
> + unsigned char id_len;
> +};
So an integer (four bytes?) is OK here? does it need to be in certain
byte order?
--
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