* Terry Lambert [EMAIL PROTECTED] [020624 19:58] wrote:
Alfred Perlstein wrote:
* Terry Lambert [EMAIL PROTECTED] [020624 19:17] wrote:
System V shared memory is allocated out of KVA space (annoying,
but true).
You keep saying this but the backing object allocated for sysvshm
Hi there,
is there a canonical way to do this? Some time ago the ability to install
man pages was removed from kmod.mk. This is reasonable for the system
itself, but for third party packages this either forces one to poke in the
internals of /usr/share/mk (not an exciting experience) or to fit
Ãкº¡Ò÷ӧҹ¢Í§¸ØáԨã¹Í¹Ò¤µ·Óä´é§èÒÂ
áÅÐÊÃéÒ§ÃÒÂä´é§ÒÁ¨Ò¡¡Ò÷ӧҹ¼èÒ¹Ãкº¼ÁÁÕÃÒÂä´éÁÒ¡¡ÇèÒ
30,000 / à´×͹ ¨Ò¡¡Ò÷ӧҹà¾Õ§ÇѹÅÐ 2-3
ªÑèÇâÁ§à·èÒ¹Ñé¹âÍ¡ÒÊÁÒ¶Ö§¤Ø³áÅéÇ
sorry for the cross posting, but didn't get much response from stable
(and it seems they are running out of disk space :-)
---BeginMessage---
em0: Intel(R) PRO/1000 Network Connection, Version - 1.2.7 and
em0: Intel(R) PRO/1000 Network Connection, Version - 1.3.8
both drivers work fine when
On Tue, 25 Jun 2002, Makoto Matsushita wrote:
I found a strange behavior of cvs (see sample session below).
Checking out the source codes seems OK, but when I update the codes with
-r and -D options, source codes are disappeared. cvs update with -r
option only is OK for me.
Is it a bug,
Hello, super guys!
Last 3 days I was trying to connect an
Aironet card PCI4800 with Cisco Aironet series 340.
No success!
Does anybody do it ??
Dimasic.
scott You could simply pop up a couple directories and checkout the
scott given tag and date over your existing checkout. CVS is smart
scott enough to notice that you've already got something checked out,
scott and it will just update things.
matusita It would be fine to me. Thank you.
Hmm,
On Tue, Jun 25, 2002 at 11:34:12PM +0600, Dmitry A. Bondareff wrote:
Last 3 days I was trying to connect an Aironet card PCI4800 with Cisco
Aironet series 340.
What EXACTLY did you try to do and what didn't work?
-- Brooks
--
Any statement of the form X is the one, true Y is FALSE.
Alfred Perlstein wrote:
You keep saying this but the backing object allocated for sysvshm
is taken from either an OBJT_PHYS or OBJT_SWAP object.
Uh, it's only ever an OBJT_SWAP; see line 532 of kern/sysv_shm.c.
Your sources seem to be really out of date...
Yes. I was referring to
* Terry Lambert [EMAIL PROTECTED] [020625 13:08] wrote:
At what point does it eat KVA that is other than for the backing
data structures?
It eats address space, not RAM. And even if the mappings are not
active (which they usually are, because of LRU and processes
accessing
:
:This is also the _default_ for how solaris manages sysv segments,
:although it would be nice if we could get the OBJT_PHYS stuff to
:use 4meg pages (unless someone already did that?)...
:
:Anyhow, I'm glad we corrected your misconception and we now have
:a more accurate understanding of how
Incidently, looking at the PV entry angle for a moment. Suppose you
create a 1GB sysvshm (pageable) segment. That's 262144 pages. Mapping this
once means you consume 262144 PV entries. At 28 bytes each, that is
about 7.3MB of KVM. Now, fork this process 300 times. The numbers become
12 matches
Mail list logo
