altq over vlan: patch exists ?
Hi guys, The configuration Altq on one interface VLAN is working on OpenBSD and DragonFlyBSD, but FreeBSD no ! exists any patch for this ? or .. why no working ? any reason ? thanx -- Luiz Gustavo Costa (Powered by BSD) *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ mundoUnix - Consultoria em Software Livre http://www.mundounix.com.br ICQ: 2890831 / MSN: cont...@mundounix.com.br ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Is the FreeBSD ABI compatibility policy documented anywhere
On Thu, 24 Sep 2009 14:00:04 -0700 Julian Elischer wrote: > Stef Walter wrote: > > It seems that FreeBSD has an ABI compatibility policy where major > > versions remain ABI and API compatible throughout minor point > > versions. That is to say that the kernel interfaces and libraries > > for (eg) 7-STABLE, 7.1-RELEASE, 7.2-RELEASE are not supposed to > > change. > > > > Is this a policy of the project? If so, is it documented anywhere? > > Or is it just a convention? > > It is a policy of the project but I don't think our policies are > written down as such. I think you will find it referenced in > many places in a sideways manner rather than directly. > > Possibly in the developer handbook The only place I found it directly referenced was in http://wiki.freebsd.org/VendorInformation -- Bruce Cran ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
sx locks and memory barriers
Hi all, looking at sys/sx.h I have some troubles understanding this comment: * A note about memory barriers. Exclusive locks need to use the same * memory barriers as mutexes: _acq when acquiring an exclusive lock * and _rel when releasing an exclusive lock. On the other side, * shared lock needs to use an _acq barrier when acquiring the lock * but, since they don't update any locked data, no memory barrier is * needed when releasing a shared lock. In particular, I'm not understanding what prevents the following sequence from happening: CPU A CPU B sx_slock(&data->lock); sx_sunlock(&data->lock); /* reordered after the unlock by the cpu */ if (data->buffer) sx_xlock(&data->lock); free(data->buffer); data->buffer = NULL; sx_xunlock(&data->lock); a = *data->buffer; IOW, even if readers do not modify the data protected by the lock, without a release barrier a memory access may leak past the unlock (as the cpu won't notice any dependency between the unlock and the fetch, feeling free to reorder them), thus potentially racing with an exclusive writer accessing the data. On architectures where atomic ops serialize memory accesses this would never happen, otherwise the sequence above seems possible; am I missing something? ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: genuine cpu I386_CPU kernel support
Julian Elischer wrote: I think a 386 can assume non-SMP in which case that can be simulated just fine :-) it also simplifies a lot of the other breakages.. #if (CPU == 80386) && defined(SMP) #error "can't have smp on a 386" #endif Paging Terry Lambert...Terry Lambert, to the hackers lounge please. Kris ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: Is the FreeBSD ABI compatibility policy documented anywhere
Stef Walter wrote: It seems that FreeBSD has an ABI compatibility policy where major versions remain ABI and API compatible throughout minor point versions. That is to say that the kernel interfaces and libraries for (eg) 7-STABLE, 7.1-RELEASE, 7.2-RELEASE are not supposed to change. Is this a policy of the project? If so, is it documented anywhere? Or is it just a convention? It is a policy of the project but I don't think our policies are written down as such. I think you will find it referenced in many places in a sideways manner rather than directly. Possibly in the developer handbook Cheers, Stef ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Is the FreeBSD ABI compatibility policy documented anywhere
It seems that FreeBSD has an ABI compatibility policy where major versions remain ABI and API compatible throughout minor point versions. That is to say that the kernel interfaces and libraries for (eg) 7-STABLE, 7.1-RELEASE, 7.2-RELEASE are not supposed to change. Is this a policy of the project? If so, is it documented anywhere? Or is it just a convention? Cheers, Stef ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
Mark Linimon escreveu: On Thu, Sep 24, 2009 at 01:35:21PM -0300, Leandro Quibem Magnabosco wrote: I think that one questions pops into the minds of a lot of people right now: Why not just use DragonFly BSD? Feel free, but take it off-list, please. mcl We (me and Luiz) did that already. Thanks and sorry. :) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
On Thu, Sep 24, 2009 at 01:35:21PM -0300, Leandro Quibem Magnabosco wrote: > I think that one questions pops into the minds of a lot of people right > now: Why not just use DragonFly BSD? Feel free, but take it off-list, please. mcl ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
Hi 2009/9/24 Leandro Quibem Magnabosco : > I think that one questions pops into the minds of a lot of people right now: > Why not just use DragonFly BSD? > > It is a pretty decent system. > Why do you need it to be FreeBSD w/ Hammer and not DragonFly BSD? exist very differences between FreeBSD and DragonFlyBSD DragonFly = fork from freebsd 4.x and other line of develop and ports/pksrc, and, and, and > > > Maybe there are some reasons, but I don't see it. > Could anybody point it out for me? > i use HAMMER on one freebsd > > Thank you. > -- > Leandro Quibem Magnabosco. > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > -- Luiz Gustavo Costa (Powered by BSD) *+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+ mundoUnix - Consultoria em Software Livre http://www.mundounix.com.br ICQ: 2890831 / MSN: cont...@mundounix.com.br ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
I think that one questions pops into the minds of a lot of people right now: Why not just use DragonFly BSD? It is a pretty decent system. Why do you need it to be FreeBSD w/ Hammer and not DragonFly BSD? Maybe there are some reasons, but I don't see it. Could anybody point it out for me? Thank you. -- Leandro Quibem Magnabosco. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
2009/9/24 Gonzalo Nemmi > On Thursday 24 September 2009 6:28:31 am Alexander Best wrote: > > i remember a discussion about HAMMER support on one of the > > mailingslists which sorta ended with the following statement: > > > > "let's get zfs running properly before we even think about starting > > with HAMMER." > > > > cheers. > > alex > > ___ > > freebsd-hackers@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > > To unsubscribe, send any mail to > > "freebsd-hackers-unsubscr...@freebsd.org" > > Yup .. that was basically it ... > Here you go: > http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/045550.html > > Regards > -- > Blessings > Gonzalo Nemmi > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org" > If the istallation get sorted out for zfs its argubly the easiest fs I have ever had to manage. There are lots of options but you dont have to use them and if you dont it wont hurt the average user. If you do decide to start using them at a later date, then its dead easy to. THe main problem with zfs is resources. If it wasn't for this then there wouldn't be a good reason not to use zfs default fs (i await the flames 8) ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
On Thursday 24 September 2009 6:28:31 am Alexander Best wrote: > i remember a discussion about HAMMER support on one of the > mailingslists which sorta ended with the following statement: > > "let's get zfs running properly before we even think about starting > with HAMMER." > > cheers. > alex > ___ > freebsd-hackers@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-hackers > To unsubscribe, send any mail to > "freebsd-hackers-unsubscr...@freebsd.org" Yup .. that was basically it ... Here you go: http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/045550.html Regards -- Blessings Gonzalo Nemmi ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
HEADSUP: Call for FreeBSD Status Reports
Dear all, I would like to remind you to submit your status reports as soon as possible. Long time has passed since the last status reports were released; and surely a lot has had happened since then. Our developers are relaxed after DevSummit and EuroBSDCon in Cambridge, which both were great! I believe a lot of stuff has been discussed during these events (I hope we will have reports covering this too) and since the last report a lot of things have happened. During that time, two other conferences have been held (BSDCan and AsiaBSDCon), we have released 7.2, not to mention that 8.0 is behind the door. Google Summer of Code should be finished by now too, and we would like to hear about its results. Surely there are a lot more projects which are currently being worked on, so please do not hesitate and write us a few lines - a short description about what you are working on, what are the plans and goals, so we can inform our community about your great work! It's useful for you as well as our users! Please note, the submissions for this quarter (well...rather halfyear, because we should now cover 4-9/2009) are due by October 7th, 2009. Please post the filled-in XML template to be found at http://www.freebsd.org/news/status/report-sample.xml to mont...@freebsd.org, or alternatively use our web based form at http://www.freebsd.org/cgi/monthly.cgi. We are looking forward to see your submissions! -- S pozdravom / Best regards Daniel Gerzo, FreeBSD committer ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
Dag-Erling Smørgrav schrieb am 2009-09-24: > Alexander Best writes: > > i remember a discussion about HAMMER support on one of the > > mailingslists which > > sorta ended with the following statement: > > "let's get zfs running properly before we even think about starting > > with > > HAMMER." > Not a valid argument; regardless of the state of ZFS, one does not > preclude the other unless you expect the same person to handle both. > The one and only reason why HAMMER is not in the base system is that > nobody has stepped forward to do it. > DES my thoughts exactly. i'd really like to use HAMMER as a ufs2 replacement on my box. zfs seems like a great fs but to me it seems too complicated to be handled by the average user. i'm really looking forward to the first few lines of code in p4. ;) cheers. alex ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: genuine cpu I386_CPU kernel support
> I honestly can't see why you would want to waste your time like this, > but it's yours to waste I suppose. (Even a notorious packrat like me > has gotten rid of hardware from that era.) > > mcl Hmm, So that's you & jhb warning me off. Well I do have a ToDo list that's a mile long, so maybe I'd best take your advice :-) Thanks all though, for the informed kernel/ assembler comment we've been reading. Cheers, Julian -- Julian Stacey: BSD Unix Linux C Sys Eng Consultants Munich http://berklix.com Mail ASCII plain text not HTML & Base64. http://asciiribbon.org Virused Microsoft PCs cause spam. http://berklix.com/free/ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
Alexander Best writes: > i remember a discussion about HAMMER support on one of the mailingslists which > sorta ended with the following statement: > > "let's get zfs running properly before we even think about starting with > HAMMER." Not a valid argument; regardless of the state of ZFS, one does not preclude the other unless you expect the same person to handle both. The one and only reason why HAMMER is not in the base system is that nobody has stepped forward to do it. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
Re: HAMMER FS port (status ?)
i remember a discussion about HAMMER support on one of the mailingslists which sorta ended with the following statement: "let's get zfs running properly before we even think about starting with HAMMER." cheers. alex ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsubscr...@freebsd.org"
