[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20170616.115928.1848639816473502604.davem@davemloft.net>
Date:   Fri, 16 Jun 2017 11:59:28 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     kafai@...com
Cc:     netdev@...r.kernel.org, ast@...com, daniel@...earbox.net,
        kernel-team@...com
Subject: Re: [PATCH v3 net-next 0/9] bpf: xdp: Report bpf_prog ID in
 IFLA_XDP
From: Martin KaFai Lau <kafai@...com>
Date: Thu, 15 Jun 2017 17:29:08 -0700
> This is the first usage of the new bpf_prog ID.  It is for
> reporting the ID of a xdp_prog through netlink.
> 
> It rides on the existing IFLA_XDP.  This patch adds IFLA_XDP_PROG_ID
> for the bpf_prog ID reporting.
> 
> It starts with changing the generic_xdp first.  After that,
> the hardware driver is changed one by one.  Jakub Kicinski mentioned
> that he will soon introduce XDP_ATTACHED_HW (on top of the existing
> XDP_ATTACHED_DRV and XDP_ATTACHED_SKB)
> and he is going to reuse the prog_attached for this purpose.
> Hence, this patch set keeps the prog_attached even though
> !!prog_id also implies there is xdp_prog attached.
> 
> I have tested with generic_xdp, mlx4 and mlx5.
 ...
Series applied, thanks Martin.
Powered by blists - more mailing lists
 
