David McDaniel wrote:
Being insufficiently familiar with kernel goings-on, I've yet to find the
answer to what someone more familiar may know off the top of the head.
Are the TLB contents saved and restored across context switches? Or are they
simply invalidated and lazily restored upon threa
David McDaniel (damcdani) wrote:
I'd try to use dtrace to get more insight but I cant figure out where
to start since I cant find the place(s) in the kernel where the dumping
is actually taking place.
core() -> do_core() -> {struct execsw->exec_core()} -> elfcore() ->
core_write()
core() i
h version of 10?)
http://www.stdlib.net/~colmmacc/2006/04/13/more-ubuntu-on-t2000/
PS: No Solaris vs Linux flames please :)
This message posted from opensolaris.org
___
perf-discuss mailing list
perf-discuss@opensolaris.org
--
Eric Lowe Solaris Ker
I posted the same question in the code group. Apparently for SPARC, the
> platform-specific files statically define the lgroups, and that many/most
> of the platform-specific files are *not* included with OpenSolaris.
Not yet. Some of these have been opened up in the last build and I bet
more
Eric Lowe wrote:
Holger Berger wrote:
I wasn't directly involved in the 64K prototype but only 64K and
larger
were used for user applications, and the page_t was 64K in span
(PAGESIZE=65536). There may have been some 8K mappings in the
kernel due
to OBP handing off translation lists
Holger Berger wrote:
I wasn't directly involved in the 64K prototype but only 64K and larger
were used for user applications, and the page_t was 64K in span
(PAGESIZE=65536). There may have been some 8K mappings in the kernel due
to OBP handing off translation lists with holes -- I don't remember
Matthew Allen wrote:
I have an application that is suffering from high iTLB misses and I'd really
like to enable VMPSS. I can create a binary with the text segment aligned on a
4M boundary, but the text is still mapped to 8K pages (as reported by pmap -xs).
Is there anything I need to do to e
David McDaniel wrote:
A binary is less 4M and demonstrates high ITLB miss rates. I decide to
experiment with making it larger to address the issue.
The first approach was to assemble the following .s file and link it into the
target binaries:
.section ".text"
.align 4096*1024
.skip 8
Thi
printf("hat_memload\n---\n");
| printf("%-16s %-50s %8s\n", "CMD", "PATH", "COUNT");
| printa("%-16s %-50s [EMAIL PROTECTED]", @path);
|
| printf("\nio:::start\n--\n");
|
Coming into this thread late since I'm returning for vacation...
On Thu, Jan 12, 2006 at 02:55:52AM +1100, Brendan Gregg wrote:
|
| I want segvn hit rate. There must be a function in the segvn code
| somewhere that checks whether a page is already in the page cache or not,
So in a nutshell, what
sent in the process address space, that's fine; ZFS
will implement its own algorithms (which are quite sophisticated) to decide
when to recycle the compressed cache copy long after the uncompressed copies
are destroyed by the paging system.
--
Eric Lowe Solaris Kernel Developmen
support for ref/mod bits (making
paging candidate determination very costly). ZFS is very fast (being copy-
on-write it does sequential I/Os whereas swapfs does random disk access),
and it supports compression. ZFS is already slated to become the new
replacement to swapfs in the near future.
--
Eric
d TLB
architecture (some sun4v CPUs have separate I/D micro TLBs but they
are invisible outside the CPU pipeline).
- Eric
--
Eric Lowe Solaris Kernel Development Austin, Texas
Sun Microsystems. We make the net work.x64155/+1(512)401
ly
8K pages the TLB has 1024 entries.
The Opteron has a 1024 entry TLB for 4K pages and a 16 entry TLB for
2M pages.
--
Eric Lowe Solaris Kernel Development Austin, Texas
Sun Microsystems. We make the net work.x64155/
ry in the "correct" range from
freelists.
--
Eric Lowe Solaris Kernel Development Austin, Texas
Sun Microsystems. We make the net work.x64155/+1(512)401-1155
___
perf-discuss mailing list
perf-discuss@opensolaris.org
ntation of swap usage, which is both confusing due to seemingly
contradictory information reported from different tools and over-
complex due to Solaris' VM observability tools exposing too many
implementation details. :(
--
Eric Lowe Solaris Kernel Development
16 matches
Mail list logo
