[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180523155047.6c136279@xeon-e3>
Date: Wed, 23 May 2018 15:50:47 -0700
From: Stephen Hemminger <stephen@...workplumber.org>
To: Björn Töpel <bjorn.topel@...il.com>
Cc: magnus.karlsson@...el.com, alexander.h.duyck@...el.com,
alexander.duyck@...il.com, john.fastabend@...il.com, ast@...com,
brouer@...hat.com, willemdebruijn.kernel@...il.com,
daniel@...earbox.net, mst@...hat.com, netdev@...r.kernel.org,
Björn Töpel <bjorn.topel@...el.com>,
michael.lundkvist@...csson.com, jesse.brandeburg@...el.com,
anjali.singhai@...el.com, qi.z.zhang@...el.com
Subject: Re: [PATCH bpf-next v3 01/15] net: initial AF_XDP skeleton
On Wed, 2 May 2018 13:01:22 +0200
Björn Töpel <bjorn.topel@...il.com> wrote:
> diff --git a/net/xdp/Kconfig b/net/xdp/Kconfig
> new file mode 100644
> index 000000000000..90e4a7152854
> --- /dev/null
> +++ b/net/xdp/Kconfig
> @@ -0,0 +1,7 @@
> +config XDP_SOCKETS
> + bool "XDP sockets"
> + depends on BPF_SYSCALL
> + default n
> + help
> + XDP sockets allows a channel between XDP programs and
> + userspace applications.
Why is XDP not supported as a module?
Most distributions will want it to be a module so that it is not loaded
unless used, and AF_XDP could be also be disabled by blacklisting the module.
Powered by blists - more mailing lists