I have read a document which tells me the following 4 things are done by the RAM embedded on disk driver controller. But I don't know what's difference between buffer and cache. Thanks!
RAM on disk drive controllers
1 firmware
2 speed matching buffer
3 prefetching buffer
4 cache (1 Reply)
Happy New Year!
There are currently four UNIX.COM achievement awards up for grabs, as the say. Here they are, in no particular order:
The Order of the Raven
The Order of the Hippo
The Order of the Spider
The Order of the Dragon
Don't ask me what they mean, or who who will get those... (0 Replies)
Dear All,
Here is the current status of the badging system:
The Beta 1 phase of the new badging system is close to completion.
42 prototype badges have been "allocated"
6 prototype badge slots are held in reserve
The "alert you have new badges" prototype is running and is currently... (4 Replies)
Here is the current array of the short description of badges for the new prototype badging system (Beta 1) with 42 icons allocated (prototype logic written) and 6 reserved (for future use);
<?php
$badges_desc = array(
"fauser" => "Total Post Count",
"faaward" => "First Post",
... (6 Replies)
Dear All,
We have a lot of amazing moderators and other very talented unix.com members who provide tireless top quality free technical support assistance to others. As a service to those long term unix.com members, I am making a new Patreon BBCODE badge available which can be posted in forum... (8 Replies)
Another major upgrade on the new UserCP today. I have created the "My Badges" page in the new control panel, and it's looking very cool :)
If you have visited the new UserCP recently, you will more-than-likely need to close your browser (completely) and then restart it to clear out the old... (2 Replies)
Discussion started by: Neo
2 Replies
LEARN ABOUT OPENSOLARIS
profile
profile(7D) Devices profile(7D)NAME
profile - DTrace profile interrupt provider
DESCRIPTION
The profile driver is a DTrace dynamic tracing provider that adds time-based interrupt event sources that can be used as DTrace probes.
Each profile event source is a time-based interrupt firing every fixed, specified time interval. You can use these probes to sample some
aspect of system state every unit time and the samples can then be used to infer system behavior. If the sampling rate is high, or the sam-
pling time is long, an accurate inference is possible. By using the DTrace facility to bind arbitrary actions to probes, you can use the
profile provider to sample practically anything in the system. For example, you could sample the state of the current thread, the CPU
state, or the current machine instruction each time a probe fires.
The profile driver is not a public interface and you access the instrumentation offered by this provider through DTrace. Refer to the
Solaris Dynamic Tracing Guide for a description of the public documented interfaces available for the DTrace facility and the probes
offered by the profile provider.
ATTRIBUTES
See attributes(5) for a description of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWdtrp |
+-----------------------------+-----------------------------+
|Interface Stability |Private |
+-----------------------------+-----------------------------+
SEE ALSO dtrace(1M), attributes(5), dtrace(7D)
Solaris Dynamic Tracing Guide
SunOS 5.11 4 Sep 2003 profile(7D)