But if you *do* happen to know 60 good programmers who are willing
to work on FreeBSD full time for very little money, let me know
and I'll see what I can do about that baby thing.
the great idea:
get a bank account, ask users if they throw an 1$ (1eur) on it and let
some indian (or something
Steven Smith [EMAIL PROTECTED] writes:
I don't know enough about Sparcs to even speculate how it's done
there.
The UltraSparc is a RISC processor, which amongst other things implies
constant instruction size. Memory barriers take care of any cache
coherence issues that may arise.
DES
--
On Mon, Jul 12, 2004 at 07:09:33PM +0100, Steven Smith wrote:
On their DTrace support forum there is the article about the problem
with different byte patterns of movl %esp, %ebp produced by
different assemblers.
Do you have an URL for that? I can't seem to find it.
Hi Andrey,
(B
(BAndrey Simonenko wrote:
(B
(B
(B Having read that bug report I began to think that they change several
(B continues bytes in a function, probably they just search for well known
(B commands sequence and atomically change one of them. I think it is
(B possible
(B to change
On Sat, 10 Jul 2004 20:45:14 +0100 in lucky.freebsd.hackers, Steven Smith wrote:
It's also possible to put probes on the return instruction of the
function. I'm not sure how they're actually finding that, though.
I think the return probe is done by adding a call probe that changes the
It's also possible to put probes on the return instruction of the
function. I'm not sure how they're actually finding that, though.
I think the return probe is done by adding a call probe that changes the
return address.
Yeah, I thought that when I first saw it, but the probe is
It's also possible to put probes on the return instruction of the
function. I'm not sure how they're actually finding that, though.
I think the return probe is done by adding a call probe that changes the
return address.
Yeah, I thought that when I first saw it, but the probe is passed the
On Wed, 7 Jul 2004, David Schultz wrote:
The page referenced earlier in this thread pointed out that 6
staff-years went into DTrace. That's accurate, and we're not
talking about part-time employees or people who don't know what
they're doing. The D compiler aside, this is not a small matter
On Thu, 8 Jul 2004, Steven Smith wrote:
It's also possible to put probes on the return instruction of the
function. I'm not sure how they're actually finding that, though.
I think the return probe is done by adding a call probe that changes the
return address.
On Thu, Jul 08, 2004 at 03:46:24AM -0400, Daniel Ellard wrote:
I don't doubt that DTrace took a long time to do. However, in most
projects the design phase consumes a lot of time, and it is often the
case that unforeseen problems or changes in the feature set cost the
developers a lot of
Hi Julian,
Julian Elischer wrote:
On Thu, 8 Jul 2004, Steven Smith wrote:
It's also possible to put probes on the return instruction of the
function. I'm not sure how they're actually finding that, though.
I think the return probe is done by adding a call probe that changes the
return
Hi,
Avleen Vig wrote:
They said 6 staff-years. This means if they have 6 people working on
it full time, it took 1 year to complete. If they had 60 people full
time, it took just over 5 weeks (technically, i doubt that would work
practically).
From speaking to a friend at sun, I do know it took a
Avleen Vig [EMAIL PROTECTED] writes:
They said 6 staff-years.
No, they said three engineers working full-time for two years.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
___
[EMAIL PROTECTED] mailing list
On Thu, Jul 08, 2004, Wilko Bulte wrote:
On Thu, Jul 08, 2004 at 01:23:04AM -0700, Avleen Vig wrote:
On Thu, Jul 08, 2004 at 03:46:24AM -0400, Daniel Ellard wrote:
I don't doubt that DTrace took a long time to do. However, in most
projects the design phase consumes a lot of time, and it
Hi Dan,
Daniel Ellard wrote:
In a nutshell, here is what DTrace is about:
- It has no impact on the system when it is not used. So you can
leave it in all the time, instead of having a debug kernel and
a production kernel.
[I don't know how they achieve the no impact but they
FreeBSD has good features such as jail, chroot e.t.c. which can controll
process or resources in parallel. So you need not port DTrace entirely.
I think the control of ressources in a jail is very limited right now. I
don't know if some work in that direction is in progress but it would be a
Hi Nicpolas,
Nicolas Bérard Nault wrote:
I think the control of ressources in a jail is very limited right now. I
don't know if some work in that direction is in progress but it would be a
great project for the future.
If you attend the prj, You can tweak as you like, I think.
Dtrace is
Dtrace is (seems, at least) to be a very powerful tool. Eventual coders
could/should get their inspiration out of the work of Sun engineers. But
remember, the volunteers of the FreeBSD project aren't paid to do what
they do. 2 years and 3 full-time engineers were needed to accomplish
Dtrace so I
Hi Nicolas,
(B
(BNicolas Be'rard Nault wrote:
(B
(B Dtrace is (seems, at least) to be a very powerful tool. Eventual coders
(B could/should get their inspiration out of the work of Sun engineers.
(B But
(B remember, the volunteers of the FreeBSD project aren't paid to do what
(B they do. 2
On Wed, Jul 07, 2004, Eitarou Kamo wrote:
FreeBSD has good features such as jail, chroot e.t.c. which can controll
Solaris 10 has these features, too, but I'm not sure what that has
to do with DTrace.
process or resources in parallel. So you need not port DTrace entirely.
You can implement
Hi David,
David Schultz wrote:
On Wed, Jul 07, 2004, Eitarou Kamo wrote:
FreeBSD has good features such as jail, chroot e.t.c. which can controll
Solaris 10 has these features, too, but I'm not sure what that has
to do with DTrace.
If You use the feature with DTrace like tool, You can
In the last episode (Jul 07), David Schultz said:
The page referenced earlier in this thread pointed out that 6
staff-years went into DTrace. That's accurate, and we're not talking
about part-time employees or people who don't know what they're
doing. The D compiler aside, this is not a
Hi Dan N,
Dan Nelson wrote:
In the last episode (Jul 07), David Schultz said:
Pawel Jakub Dawidek has already written a C-like language for his
Cerber project that looks like it could be used for a FreeBSD DTrace.
It doesn't support associative arrays for stat collecting like D does,
but it's
Hi;
The article suggests we should learn from Solaris and implement closefrom(3C):
http://www.freebsd.org/cgi/man.cgi?query=closefromapropos=0sektion=0manpath=SunOS+5.9format=html
And make sure we use it in sendmail (and Javac).
cheers,
Pedro.
In a nutshell, here is what DTrace is about:
- It has no impact on the system when it is not used. So you can
leave it in all the time, instead of having a debug kernel and
a production kernel.
[I don't know how they achieve the no impact but they claim
that
On Wed, Jun 30, 2004, Bruce M Simpson wrote:
This recently caught my eye:
http://www.samag.com/documents/s=9171/sam0406h/0406h.htm
There are a number of good sounding suggestions in there.
DTrace is pure magic. It would be well worth your time to install
Solaris 10 just to try out DTrace
HI Schultz and all,
(B
(BDavid Schultz wrote:
(B
(B On Wed, Jun 30, 2004, Bruce M Simpson wrote:
(B
(B
(B This recently caught my eye:
(B http://www.samag.com/documents/s=9171/sam0406h/0406h.htm
(B
(B There are a number of good sounding suggestions in there.
(B
(B
(B DTrace is pure
Hi,
David Schultz wrote:
On Wed, Jun 30, 2004, Bruce M Simpson wrote:
This recently caught my eye:
http://www.samag.com/documents/s=9171/sam0406h/0406h.htm
There are a number of good sounding suggestions in there.
DTrace is pure magic. It would be well worth your time to install
Solaris
In local.freebsd-hackers, you wrote:
I haven't seen above well yet. But A article says that DTrace sounds
like 30,000 lines of debug print.
No, already the first article tells you that they use a VM with byte-code
for the C-like language D. And it's not compiled into the kernel but
hooked in
Hi Volker and all,
Volker Stolz wrote:
In local.freebsd-hackers, you wrote:
I haven't seen above well yet. But A article says that DTrace sounds
like 30,000 lines of debug print.
No, already the first article tells you that they use a VM with byte-code
for the C-like language D. And it's
Hi,
Eitarou Kamo wrote:
No, already the first article tells you that they use a VM with
byte-code
for the C-like language D. And it's not compiled into the kernel but
hooked in and removed on-the-fly.
I don't know langage D well. But my guess is that they trim the info
valuable from the debug
This recently caught my eye:
http://www.samag.com/documents/s=9171/sam0406h/0406h.htm
There are a number of good sounding suggestions in there.
BMS
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To
On Tuesday 29 June 2004 09:16 pm, Bruce M Simpson wrote:
This recently caught my eye:
http://www.samag.com/documents/s=9171/sam0406h/0406h.htm
There are a number of good sounding suggestions in there.
They gave a paper on it at USENIX ATC as well.
--
John Baldwin [EMAIL PROTECTED]
33 matches
Mail list logo
