Alfred Perlstein [EMAIL PROTECTED] writes:
Hi guys, we need critical sections for userland here.
This is basically to avoid a process being switched out while holding
a user level spinlock.
Yeah, great idea, cooperative multitasking is the new black!
DES
--
Dag-Erling Smørgrav - [EMAIL
Alfred Perlstein [EMAIL PROTECTED] writes:
Do you have:
a) Evidence or a paper to prove that this is a bad idea?
I need evidence or a paper to prove that it is a bad idea to allow a
userland process to hold the CPU indefinitely?
b) A helpful suggestion?
Why don't you tell us what you're
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 02:05] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Hi guys, we need critical sections for userland here.
This is basically to avoid a process being switched out while holding
a user level spinlock.
Yeah, great idea, cooperative
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 03:01] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Do you have:
a) Evidence or a paper to prove that this is a bad idea?
I need evidence or a paper to prove that it is a bad idea to allow a
userland process to hold the CPU
Alfred Perlstein [EMAIL PROTECTED] writes:
It's not worth my time to engage someone with your mind set, you
posses neither the technical nor interpersonal skill to be useful
to me.
This could be the beginning of a wonderful friendship...
For context see my replies in this thread to Kip Macy
What PCI 32/33 S-ATA controller is recommended for a x86/FreeBSD-6 system
that is stable and reliable in terms of hardware design, and software drivers ?
My current Promise card is said to abuse PCI burst mode, in essence it will
exploit to tight timing margins. And the motherboard doesn't have
Quoting Alfred Perlstein, who wrote on Thu, Oct 04, 2007 at 03:19:02AM -0700 ..
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 03:01] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Do you have:
a) Evidence or a paper to prove that this is a bad idea?
I need evidence or a
Hello,
How to distinguish if /dev/da* devices are internal scsi drivers or
LUNs of
external SAN?
Is there any tool?
Thanks for any advice.
Sharad Chandra
___
freebsd-hackers@freebsd.org mailing list
Sharad Chandra wrote:
Hello,
How to distinguish if /dev/da* devices are internal scsi drivers or LUNs of
external SAN?
camcontrol devlist -v
Might help you..
Eric
___
freebsd-hackers@freebsd.org mailing list
On Thu, 4 Oct 2007, Alfred Perlstein wrote:
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 03:01] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Do you have:
a) Evidence or a paper to prove that this is a bad idea?
I need evidence or a paper to prove that it is a bad idea to allow a
Peter B wrote:
What PCI 32/33 S-ATA controller is recommended for a x86/FreeBSD-6 system
that is stable and reliable in terms of hardware design, and software drivers ?
My current Promise card is said to abuse PCI burst mode, in essence it will
exploit to tight timing margins. And the
Quoting Sharad Chandra, who wrote on Thu, Oct 04, 2007 at 05:25:00PM +0530 ..
Hello,
How to distinguish if /dev/da* devices are internal scsi drivers or
LUNs of
external SAN?
Is there any tool?
/var/run/dmesg.boot I would think. And then you would need to map
things manually.
On 2007-10-02 15:41, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/2/07, Dag-Erling Sm?rgrav [EMAIL PROTECTED] wrote:
Vlad GALU [EMAIL PROTECTED] writes:
The symptoms were exhibited even with rev. 1.16. I've CC'ed him so
he can catch up with the thread.
Which symptoms? I can no longer
On 10/4/07, Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2007-10-02 15:41, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/2/07, Dag-Erling Sm?rgrav [EMAIL PROTECTED] wrote:
Vlad GALU [EMAIL PROTECTED] writes:
The symptoms were exhibited even with rev. 1.16. I've CC'ed him so
he can catch
On 2007-10-04 18:05, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/4/07, Giorgos Keramidas [EMAIL PROTECTED] wrote:
On 2007-10-02 15:41, Vlad GALU [EMAIL PROTECTED] wrote:
On 10/2/07, Dag-Erling Sm?rgrav [EMAIL PROTECTED] wrote:
Vlad GALU [EMAIL PROTECTED] writes:
The symptoms were exhibited even with
Sharad Chandra wrote:
Hello,
How to distinguish if /dev/da* devices are internal scsi drivers or LUNs of
external SAN?
Is there any tool?
Thanks for any advice.
Sharad Chandra
___
freebsd-hackers@freebsd.org mailing list
* Wilko Bulte [EMAIL PROTECTED] [071004 04:15] wrote:
Quoting Alfred Perlstein, who wrote on Thu, Oct 04, 2007 at 03:19:02AM -0700
..
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 03:01] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
Do you have:
a) Evidence or a paper to
* Daniel Eischen [EMAIL PROTECTED] [071004 06:05] wrote:
His point about telling us what you're really doing, so we might
off other ways to do it is valid.
We don't know why you are using homegrown user-level spinlocks
instead of pthread mutexes. Priority ceiling mutexes and running
in
* Dag-Erling Sm??rgrav [EMAIL PROTECTED] [071004 03:28] wrote:
Alfred Perlstein [EMAIL PROTECTED] writes:
It's not worth my time to engage someone with your mind set, you
posses neither the technical nor interpersonal skill to be useful
to me.
This could be the beginning of a wonderful
On Thu, 4 Oct 2007, Alfred Perlstein wrote:
* Daniel Eischen [EMAIL PROTECTED] [071004 06:05] wrote:
His point about telling us what you're really doing, so we might
off other ways to do it is valid.
We don't know why you are using homegrown user-level spinlocks
instead of pthread mutexes.
2007/10/3, Alfred Perlstein [EMAIL PROTECTED]:
* Daniel Eischen [EMAIL PROTECTED] [071002 19:46] wrote:
On Tue, 2 Oct 2007, Alfred Perlstein wrote:
Hi guys, we need critical sections for userland here.
This is basically to avoid a process being switched out while holding
a user level
Attilio Rao wrote:
2007/10/3, Alfred Perlstein [EMAIL PROTECTED]:
* Daniel Eischen [EMAIL PROTECTED] [071002 19:46] wrote:
On Tue, 2 Oct 2007, Alfred Perlstein wrote:
Hi guys, we need critical sections for userland here.
This is basically to avoid a process being switched out while holding
On Oct 4, 2007, at 10:43 AM, Daniel Eischen wrote:
On Thu, 4 Oct 2007, Alfred Perlstein wrote:
* Daniel Eischen [EMAIL PROTECTED] [071004 06:05] wrote:
His point about telling us what you're really doing, so we might
off other ways to do it is valid.
We don't know why you are using
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more appropiate for this
Peter B wrote:
3ware 9650 in RAID6 mode with firmware version 3.08.00.004 seems to cause
data corruption when rebuilding a single disc with raid6.
http://www.webmasternetwork.se/f4t23551.html (Swedish)
I thought this was serious enough for people to know. If another mailinglist
is more
25 matches
Mail list logo
