GEOM + Vinum

2004-01-17 Thread Lukas Ertl
Hi -hackers, following the recent discussion about GEOM and Vinum I wrote some proof-of-concept code, or rather, I copy'n'pasted the necessary stuff for a prototype. Of course it's ugly, it's buggy, it's by far not complete, but at least it understands the most basic setup: a volume with a single

Re: ip_input - chksum - why is it done so early in ip_input?

2004-01-17 Thread Robert Watson
On Sat, 17 Jan 2004, Andre Oppermann wrote: > > Besides that i'd like to add that FreeBSD has the fastest forwarding engine > > i've seen on any free OS. It's in my opinion a very suitable OS for > > routing/forwarding. > > We are working on it to make it even faster. If you are using 5.2 or >

Re: ip_input - chksum - why is it done so early in ip_input?

2004-01-17 Thread Andre Oppermann
Sten Daniel Sørsdal wrote: > > Apologies for the cross-post, i wasnt sure if this was hackers or net material. > > I've often wondered why ip checksumming is done on every incoming > packet and not only on the packets that need to be delivered locally. Only the IP header checksum is checked. We

Re: [CHECKER] bugs in FreeBSD

2004-01-17 Thread M. Warner Losh
In message: <[EMAIL PROTECTED]> Paul Twohey <[EMAIL PROTECTED]> writes: : Hi, : : I'm with the Stanford Metacompilation research group. We have a suite of : checkers that find bugs at compile time and we've had quite a bit of : success checking the Linux kernel code for errors. Since o

Re: __restrict__ vs __restrict ?

2004-01-17 Thread Ruslan Ermilov
On Sat, Jan 17, 2004 at 09:19:28AM -0800, David O'Brien wrote: > On Fri, Jan 16, 2004 at 08:03:05PM -0800, Tim Kientzle wrote: > > >No, we should be using the __restrict as coded. But I wonder why > > >we can't just use "restrict"... > > > > Because that would really mess up any user program that

Re: __restrict__ vs __restrict ?

2004-01-17 Thread David O'Brien
On Fri, Jan 16, 2004 at 08:03:05PM -0800, Tim Kientzle wrote: > >No, we should be using the __restrict as coded. But I wonder why > >we can't just use "restrict"... > > Because that would really mess up any user program that used > 'restrict' as a variable or function name. I think the > current