> But you haven't even studied how the Linux networking works, so how > would you know? I guess time is better spent reinventing the wheel. > Since you don't know, by definition you're spewing. You don't know > the Linux networking, and therefore you don't know whether existing > mechanisms can solve your problem or not.
First of all, thanks for the pointer to XFRM. I have tried to find information about it, but this is few and far between. For example, mailing list messages about a 3COM 3CR990 patch for IPSEC offloading are easily missed. About your remark: I have studied linux networking so far as it has crossed my path. IPSEC, the only place for which XFRM is being used it seems, was scheduled for later. You don't expect to see a different framework in a subset of the stack. Also, I don't see how this invalidates my use of another streams-like framework any more than the existence of STREAMS in solaris does. XFRM is pretty much tailored to its use-case. FFPF (what I'm working on) is in its own right. Does XFRM support big & little endian hardware to work on the same structures? Does is support transparent context-switch reduction and zero-copy? If so, then it is unfortunate that I didn't find out before. Which brings me to point two. My network subsystem knowledge comes mostly from previously published work at academic venues -- as I wrote before. This is accepted procedure in scientific circles (even applied science like systems research). The underlying idea is that if implementations (Linux, Windows, Plan9) are innovative in any way, those features would have been published about independently in the same venues (or at least the Linux Symposium, BSDCon, ..). It appears the communities don't mix enough. Publish what you have, if it's new. Why? because if you don't you can make a snide remark to one guy that he didn't study linux, but how many systems should a person study before you start coding? Is it ok to know just linux? or should I also know all internals of NetBSD? What about WindowsNT, Plan9, VMS, IOS? You can reprimande me, but there are countless others who will make the same 'mistake'. In short, I would love to build on top of your work, instead of having to deal with the same kernel panic you probably encountered a few years ago. But first of all the system you point to doesn't seem appropriate for my research. More importantly, even if it had, I didn't come across it in time. You're opinion is that this is my fault, that I didn't read through enough code and mailing list messages. I believe this is only partly the truth. Equally important is that your work wasn't brought to publicly attention throught he standard method (i.e. publishing a paper). If - on the other hand - you don't care about these things, that's okay too. But then reprimanding someone afterwards for not having heard of your work is a bit odd. By the way, I never meant to start a discussion about this topic. It seems out-of-place in a net-dev mailing list. As you threw the ball, though, it's only decent to return it. > Is research funding that hard to obtain these days? was this really necessary? respectfully, Willem - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
