Steven Hartland wrote:
Another observation from my recent dealings with using
NFS based /usr is that the remote critical mounts via
nfs dont always give the network enough time to
initialise before running. The first error displayed
is:
Mounting NFS file systems:mount_nfs: nfs1: hostname nor
Hello,
I think i've seen somewhere but i don't remember that floating point
arithmetic is not allowed in kernel space, if that's right, can anyone
please tell why ???
and why not not emulate the floating point in kernel space ???
Thanks
--
I'm Searching For Perfection,
So Even If U Need
Steven Hartland wrote:
Doug Barton wrote:
Steven Hartland wrote:
Given that it sounds like a potential workaround is to use the
machines IP instead of name until this is fixed, thanks for the info
guys.
For as long as I can remember, it's been a Best Practice to have
Julian Elischer wrote:
Markus Boelter wrote:
Apart from wondering how you're getting the motherboard to get past
POST without RAM, I'm wondering how you'd get the bootloader and
[...]
The guys at Linux/OpenBIOS did some Cache-as-RAM stuff. Maybe you can
also put
Maslan [EMAIL PROTECTED] wrote:
I think i've seen somewhere but i don't remember that floating point
arithmetic is not allowed in kernel space, if that's right, can anyone
please tell why ???
Because the overhead of swapping the contents of the FPU
registers on every context switch within
Oliver Fromme wrote:
For FreeBSD, I think a workable solution would be to
write a new RC script (e.g. /etc/rc.d/port_up) that
polls the configured interfaces and waits until they
are up. It should have a configurable timeout so it
won't hang forever. Then add it to the REQUIRE line
of the
hi
when looking at PR103455 I found this and I have a question..
code:
swp_pager_strategy(bp);
/*
* wait for the page we want to complete. VPO_SWAPINPROG is always
* cleared on completion. If an I/O error occurs, SWAPBLK_NONE
* is set in the meta-data.
On Fri, 23 Feb 2007 10:56:17 +0700 Eugene Grosbein wrote:
On Thu, Feb 22, 2007 at 12:37:00PM -0500, Zaphod Beeblebrox wrote:
Peter Jeremy wrote:
I've found that you do get a worthwhile improvement in dump|restore
performance by introducing a large (10's of MB) fifo between them.
This
Steven Hartland wrote:
Oliver Fromme wrote:
For FreeBSD, I think a workable solution would be to
write a new RC script (e.g. /etc/rc.d/port_up) that
polls the configured interfaces and waits until they
are up. It should have a configurable timeout so it
won't hang forever. Then
Oliver Fromme wrote:
I had FreeBSD 2.2-stable installed on an old notebook with
4 MB RAM (actually less, because ~ 0.5 MB was lost VGA
mappings and registers etc.). It was very usable for
simple things like text editing and as a terminal.
High end Xeons and Itaniums have 18MB - 24MB of
Hi Community,
I hope that i send this mail to the rigth place.
I'm trying to make authentication using the pam_radius, but i have
some issues that i don't know if it possible to manage.
Is that possible to configure this module to send also other
attributes like Calling-Station-Id on the
On 3/9/07, Oliver Fromme [EMAIL PROTECTED] wrote:
Maslan [EMAIL PROTECTED] wrote:
I think i've seen somewhere but i don't remember that floating point
arithmetic is not allowed in kernel space, if that's right, can anyone
please tell why ???
Because the overhead of swapping the contents of
Divacky Roman wrote:
hi
[snip]
is my analysis correct? if so, can the race be mitigated by moving the flag
setting (hence
also the locking) after the msleep()?
No. When the wakeup is performed, the VPO_SWAPINPROG flag is also
cleared. Both operations occur in the I/O completion
Ivan Voras wrote:
Oliver Fromme wrote:
I had FreeBSD 2.2-stable installed on an old notebook with
4 MB RAM (actually less, because ~ 0.5 MB was lost VGA
mappings and registers etc.). It was very usable for
simple things like text editing and as a terminal.
High end Xeons and
Steven Hartland wrote:
Although that sounds like a possible solution I wouldnt
be suprised if there are other services which REQUIRE
NETWORKING and make assumptions about the network
state which are currently invalid.
Given this perhaps NETWORKING is where this fix should
really be
Any change this can be included officially at some point?
I did not write the code. Just patched it so it would compile in 6.2
Thanks!
Jan
http://www.digitaldaemon.com/FreeBSD/FreeBSD/index.html
___
freebsd-hackers@freebsd.org mailing list
Does FreeBSD have anything similar to Futexes for
Linux.
Thanks,
Peter
Looking for earth-friendly autos?
Browse Top Cars by Green Rating at Yahoo! Autos' Green Center.
http://autos.yahoo.com/green_center/
umtx
On 3/9/07, Peter Holmes [EMAIL PROTECTED] wrote:
Does FreeBSD have anything similar to Futexes for
Linux.
Thanks,
Peter
Looking for earth-friendly autos?
Browse Top Cars by Green Rating at Yahoo!
Kip Macy wrote:
umtx
[EMAIL PROTECTED]:man -k umtx
umtx: nothing appropriate
[EMAIL PROTECTED]:
also if you use umtx I think you limit yourself to libthr.
On 3/9/07, Peter Holmes [EMAIL PROTECTED] wrote:
Does FreeBSD have anything similar to Futexes for
Linux.
Thanks,
Peter
I think i've seen somewhere but i don't remember that floating point
arithmetic is not allowed in kernel space, if that's right, can anyone
please tell why ???
and why not not emulate the floating point in kernel space ???
That's nonsense! Floating point arithmetic is absolutely allowed in
And? With futexes you limit yourself to whatever library provides
pthread wrappers around them. He asked for the FreeBSD equivalent and
the answer is umtx.
Can you provide us with some concrete examples where libkse is preferable?
-Kip
On 3/9/07, Julian Elischer [EMAIL
Do you think that the umtx KPI may have reached the appropriate level
of maturity for writing up a man page? The KSE equivalent has had a
substantive man page for quite some time. I would be more than happy
to do any of the necessary technical copy-editing for the English.
At this point I think
On 3/10/07, Kip Macy [EMAIL PROTECTED] wrote:
umtx
Is it safe/recommended to use spinlocks, like in jemalloc, for very
small portions of code? I'm particularly interested in protecting
writes to a couple of word sized ints on amd64, so the critical
section wouldn't be longer than two
On Fri, 9 Mar 2007, Kip Macy wrote:
Do you think that the umtx KPI may have reached the appropriate level of
maturity for writing up a man page? The KSE equivalent has had a substantive
man page for quite some time. I would be more than happy to do any of the
necessary technical copy-editing
On Sat, 10 Mar 2007, Vlad GALU wrote:
On 3/10/07, Kip Macy [EMAIL PROTECTED] wrote:
umtx
Is it safe/recommended to use spinlocks, like in jemalloc, for very small
portions of code? I'm particularly interested in protecting writes to a
couple of word sized ints on amd64, so the critical
Hi Jan,
The problem with your patch is the missing IPv6 support. The
drafonfly version already supports it.
Regards,
Janos Mohacsi
Network Engineer, Research Associate, Head of Network Planning and Projects
NIIF/HUNGARNET, HUNGARY
Key 70EF9882: DEC2 C685 1ED4 C95A 145F 4300 6F64 7B00
26 matches
Mail list logo
