On Tue, 7 Feb 2017 21:51:49 +0100 Jesper Dangaard Brouer <brouer@xxxxxxxxxx> wrote: > 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? One of the real problems with the kernel's documentation is that there is really almost no thought given to who the audience is. We have docs for kernel developers, for system admins, for user-space developers, etc., and it's all mixed up into one big jumble. An objective of mine in launching into this whole project is to try to fix that, so that people can readily find the documentation they need. So I don't think a single top-level directory, with a mix of user-space API info and "internals", is the right direction to go. The internals docs should, IMO, go elsewhere, probably in the core-api manual. See what I'm getting at here? > And it seems Daniel is proposing capital-letters BPF for the directory > name "Documentation/BPF/"? Any opinions on that? (I'm neutral) I think we should paint it green; otherwise I'm not too concerned about this particular point...:) Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
