lkml.org 
[lkml]   [2002]   [Jun]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: of ethernet names (was [PATCH] Futex Asynchronous
Date
On Tue, 11 Jun 2002 09:36, Randy.Dunlap wrote:
> On Tue, 11 Jun 2002, Brad Hards wrote:
> | On Tue, 11 Jun 2002 09:20, Paul Menage wrote:
> | > In article
> | > <0C01A29FBAE24448A792F5C68F5EA47D29DD32@nasdaq.ms.ensim.com>,
> | >
> | > you write:
> | > >Is there any documentation on the netlink API, beyond UTSL(iproute)?
> | > >Reference would be good, but a tutorial would be ideal.
> | >
> | > The man pages for netlink(3), netlink(7), rtnetlink(3) and rtnetlink(7)
> | > give a basic reference.
> |
> | Unfortunately my brain is not on the same level and scope as Alexey or
> | davem.
> |
> | I simply don't grok those pages. I also note caveats about
> | incompleteness, and recommendation to use libnetlink, which is also not
> | documented much.
>
> Hi Brad,
>
> There was an announcement earlier today of some networking
> documentation. I think that it's still in its early stages, though.
Very early, from my review :)

> From the 'netdev' list:
>
> Hi,
>
> I am working on a doc on "Networking Subsystem" in the Linux kernel.
> This
> is part of the "Linux Kernel documentation project" (www.lkdp.tk).
And this is the wrong focus (for me). I need documentation from the userspace
view. The documentation I need shouldn't try to explain how the kernel works,
except as needed to understand what to do in userspace. My concept is
something like the tutorial I am working on for Linux HID programming
(explaination of the various interfaces and options - see
http://www.frogmouth.net/hid-doco/linux-hid.html for an early draft).

Not to suggest we shouldn't document the kernel mechanics - this is important
too.

But kernel programmers need to remember that user space programmers will take
the path of least resistance when trying to interact with the kernel. Good
documentation and easy-to-copy examples beats a slightly more powerful API
(where slightly depends on being able to accomplish task in both APIs, even
if it gets ugly) every time. If you want people to switch over to your new
API/ABI, its got to be easy.
--
http://conf.linux.org.au. 22-25Jan2003. Perth, Australia. Birds in Black.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:22    [W:0.098 / U:1.748 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site