From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jesper Dangaard Brouer Subject: Re: [net-next PATCH 0/4] Documenting eBPF - extended Berkeley Packet Filter Date: Tue, 7 Feb 2017 21:51:49 +0100 Message-ID: <20170207215149.55d17098@redhat.com> References: <148647756092.10567.10947541548678801938.stgit@localhost> <20170207083717.1c98f608@lwn.net> <20170207170908.492d71c0@redhat.com> <20170207094608.60897ee0@lwn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, linux-doc@vger.kernel.org, Alexei Starovoitov , alexander@alemayhu.com, linux-kernel@vger.kernel.org, quentin.monnet@6wind.com, Daniel Borkmann , brouer@redhat.com To: Jonathan Corbet Return-path: In-Reply-To: <20170207094608.60897ee0@lwn.net> Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Tue, 7 Feb 2017 09:46:08 -0700 Jonathan Corbet wrote: > On Tue, 7 Feb 2017 17:09:08 +0100 > Jesper Dangaard Brouer wrote: > > > > > Question: What kernel tree should this go into??? > > > > > > > > If going through Jonathan Corbet, will it appear sooner here??? > > > > https://www.kernel.org/doc/html/latest/ > > > > What about this question? Or let me ask in another way, what tree is > > https://www.kernel.org/doc/html/latest/ based on? > > I believe it's generated from the current -rc. If this stuff goes into > 4.11, it should show up there next week. > > > Yes, I was also wondering hard where to put it... and a book for > > user-space developer documentation would likely be the right place, but > > it was not there, as you mention ;-) > > > > I'm fine with moving it later under another "book". Linking to it as > > HTML would still be the same right? (https://www.kernel.org/doc/html/latest/bpf/index.html) > > And is the Documentation/bpf/ directory the correct place? > > Moving it would change the URL, of course. If we want to avoid that, we > should try to come up with the proper placement from the outset. And we > would want to move it; I really want to clean up the mess that is the > top-level directory. > > How about if it goes into Documentation/userspace-guide/bpf ? The > intermediate directory could just be empty for now, I'll put the book > structure into place later on. Then the URL for the BPF guide itself > wouldn't change. I sounds like Daniel (see other email) have bigger plans for what Documentation/BPF/ should contain. E.g. consolidating Documentation/networking/filter.txt which covers the cBPF/eBPF internals. If that is the case (and I like the idea), then it goes beyond a "userspace-guide". And perhaps "BPF" is a "book" of its own? And it seems Daniel is proposing capital-letters BPF for the directory name "Documentation/BPF/"? Any opinions on that? (I'm neutral) -- Best regards, Jesper Dangaard Brouer MSc.CS, Principal Kernel Engineer at Red Hat LinkedIn: http://www.linkedin.com/in/brouer