Hi list and Michael -
I received a T470s at work and decided to jump into the CURRENT end of the
FreeBSD pool. I have a weird acpi_ibm issue and I'm not sure where to start
trying to diagnose the issue.
# uname -a
FreeBSD spanner 12.0-CURRENT FreeBSD 12.0-CURRENT #0 r328126: Thu Jan 18
15:25:44
Answering Terry's comment about LFS:
I had about 90% of the LFS development complete
(rewritten to eliminate much of the unnecessary
and inefficient copying.) At that time, Kirk
had started softupdates, but I also KNEW and
UNDERSTOOD the limitations of LFS.
In essense, after CAREFULLY reading
Gang:
The problem with measuring the dynamic slowdown is that
some of the overhead can be hidden by the kernel (e.g.
prezeroing.)
(Sorry for not directly replying -- my email filtering is
wierd.)
John
___
Tim Kientzle said:
Richard Coleman wrote:
It seems /bin/sh is the real sticking point.
There is a problem here: Unix systems have historically used
/bin/sh for two somewhat contradictory purposes:
* the system script interpreter
* as a user shell
The user shell must be
Guys,
Please revisit the dynamic linking for everything. The
cost for using shared libs in cases like shells actually
is higher than statically linking (both in memory and
in time.) It appears that there is a loss of VM understanding
over time. Don't
M. Warner Losh said:
In message: [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: It really doesn't make sense to arbitrarily cut-off a
: discussion especially when a decision might be incorrect.
I'd say that good technical discussion about why this is wrong would
be good.
Scott Long said:
On Tue, 18 Nov 2003 [EMAIL PROTECTED] wrote:
M. Warner Losh said:
In message: [EMAIL PROTECTED]
[EMAIL PROTECTED] writes:
: It really doesn't make sense to arbitrarily cut-off a
: discussion especially when a decision might be incorrect.
masta said:
One of ther things he might have forgot to mention is dynamic tricks
releated to PAM, which sorta falls in the same league as NSS working out
of the box. It was worth mentioning IMHO.
I guess that I have to remember that my own goals of 'performance'
and handling 'highest
Scott Long said:
On Tue, 18 Nov 2003 [EMAIL PROTECTED] wrote:
The cool thing about properly implemented shared libs is that not everything
has to be shared. Even the kernel supports runtime loading/addition
of modules, and the NSS sounds like a good candidate for a library
feature.
Gordon Tetlow said:
On Tue, Nov 18, 2003 at 08:03:23PM -0500, [EMAIL PROTECTED] wrote:
However, PAM and NSS 'tricks' really seem to be exactly that,
and certainly worthy of special builds. However, that isn't
necessary, yet still not building everything with a shared
libc.
Things
Gang,
I suspect that my position has been expressed
adequately.
Further discussion might become divisive, but
a decision that incurs the overhead of performance
or a rebuild on the default user base seems
wrong (JUST MY OPINION.) It took ALOT of
Matthew Dillon said:
: global references across subroutine calls! I'll send Luoqi another email.
:
: In the case of the NFS stuff, the changes have been pretty well tested
: so I think we are in the clear.
:
:On a somewhat similar note, what do you think about converting a lot
Matthew Dillon said:
: Well, the issue with converting many of the macros to inline functions
: is with the embedded goto's and references to variables defined outside
: the macros. Converting them to functions would basically require
: rewriting a huge chunk of NFS code.
per-processor registers that one could use (but loading a
general register with that per processor register would be
needed for access.) Also, since the PPC has lots of registers,
one could? permanently reserve one of the general registers (r13?).
I really don't like the idea of
Alan Cox said:
I've committed the basic infrastructure to improve TLB management
on SMPs. Translation: this will lead to the elimination of a LOT
of interprocessor interrupts to invalidate TLB entries. I'll be
turning on the new mechanisms slowly so we can carefully debug
each step and
Soren Schmidt said:
DMA support has been added to the ATA disk driver.
This only works on Intel PIIX3/4, Acer Aladdin and Promise controllers.
The promise support works without the BIOS on the board,
and timing modes are set to support up to UDMA speed. This
solves the problems with having
Michael E. Mercer said:
Hello,
This was posted to freebsd-questions with no reply.
I tried this and the child process created a core file.
I also tried the other options and they seem to work.
Just RFPROC and RFMEM DON'T!
rfork(RFMEM) doesn't easily work from C. You need to
create an
On Sat, 20 Mar 1999, John S. Dyson wrote:
Michael E. Mercer said:
Hello,
This was posted to freebsd-questions with no reply.
I tried this and the child process created a core file.
I also tried the other options and they seem to work.
Just RFPROC and RFMEM DON'T
Matthew Dillon said:
:There're a couple of places in swtch.s where code looks like this,
:
:#ifdef VM86
:btrl%esi, _private_tss
:je 3f
: ...
:3:
:#endif
:
:The conditional jump statement doesn't seem right, according to manual,
:btrl instruction modifies CF
Eivind Eklund said:
On Tue, Nov 17, 1998 at 09:49:31PM -0500, HighWind Software Information wrote:
After installing the recent libc_r and libc, I'm getting:
ld.so failed: Undefined symbol SYS_kldsym in
make:/usr/lib/aout/libc.so.3.1
I also get it sometimes when I link against
Eivind Eklund said:
On Mon, Mar 08, 1999 at 05:59:05PM -0500, John S. Dyson wrote:
Eivind Eklund said:
If you do not know how FreeBSD works to a detailed enough level to NOT
HAVE TO ASK THIS, then you should MAKE WORLD. You should NOT try to
do incremental recompiles
Brian Feldman said:
The lock manager isn't bright enough to detect that the process
already holds a read lock when it attempts to get the write lock.
Thus, you get the thrd_sleep instead of a panic.
In short, same bug, different symptoms.
Ahh, makes sense.
Quick question: how
John Polstra said:
In article 19990228152909.e2...@relay.nuxi.com,
David O'Brien obr...@nuxi.com wrote:
I keep on hearing about how we're losing because we don't have the 3
month old latest feature
With EGCS the issue isn't having the latest 3 mo. feature, but we have a
totally
Jordan K. Hubbard said:
I can generally build a kernel with EGCS, if I change how the .text and
.data are laid out for initialized data. It seems that the initialization
code makes assumptions about the order or layout of the initialization
data. Once the stuff is made to act more like
Chuck Robey said:
On Mon, 1 Mar 1999, John S. Dyson wrote:
I can generally build a kernel with EGCS, if I change how the .text and
.data are laid out for initialized data. It seems that the initialization
code makes assumptions about the order or layout of the initialization
data
John Polstra said:
John S. Dyson wrote:
Jordan K. Hubbard said:
I can generally build a kernel with EGCS, if I change how the .text and
.data are laid out for initialized data. It seems that the
initialization
code makes assumptions about the order or layout of the initialization
Martin Cracauer said:
In 199902230725.caa02...@y.dyson.net, John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs
Luoqi Chen said:
Do you still have that piece of code? Does it handle the case involves more
than one process? For example, process 1 mmaps file B and reads file A into
the mmapped region, while process 2 mmaps file A and reads file B, this could
also result in a deadlock.
It used to be
Søren Schmidt said:
It seems John S. Dyson wrote:
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine
Luoqi Chen said:
This seems to be the good old vnode deadlock during vm_fault() that has been
reported a couple of times, and there's still no satisfactory solution to it:
fgrep does something like this: (don't ask me why)
addr = mmap(0, len, PROT_READ|PROT_WRITE, MAP_PRIVATE, fd,
Søren Schmidt said:
It should work, but the promise support in the old system is, well,
hacky at best. I'm not sure if Promise supports more than one card
at a time, but from looking at the chip specs, it should work just
fine, and if the hardware works, at least the new driver will support
Julian Elischer said:
On Tue, 16 Feb 1999, Luoqi Chen wrote:
You may try my patch at http://www.freebsd.org/~luoqi, which would allow
linux threads to run on SMP.
I've gone through these patches and I can see that they are really needed
for SMP where address spaces are shared.
I
Matthew Dillon said:
:maxusers 256
Try reducing maxusers to 128. Another person reported similar behavior
to me and after a bunch of work he tried going back to a basic
distribution -- and everything started working again.
It turned out that a maxusers value of 256
Matthew Dillon said:
Ah, interesting. I understand the second bit. The first bit seems
somewhat odd, though - the automatic page coloring adjustment made
by _vm_object_allocate() doesn't work well enough for kmem_object?
The problem with it was that there appeared to be a
Matthew Dillon said:
: next_index += PQ_L2_SIZE/4;
: if (next_index PQ_L2_MASK)
: next_index = (next_index + 1) PQ_L2_MASK;
Oops, make that:
next_index += PQ_L2_SIZE/4;
if (next_index PQ_L2_MASK)
next_index = (next_index +
Matthew Dillon said:
Ah, interesting. I understand the second bit. The first bit seems
somewhat odd, though - the automatic page coloring adjustment made
by _vm_object_allocate() doesn't work well enough for kmem_object?
There appears to be a clash. I haven't really carefully
When reviewing the VM code regarding another issue (another significant
VM contributor had found an interesting anomoly), I noticed that the
coloring wasn't as complete as it should be.
Attached is a patch that appears to make a reasonable improvement in
performance, when using both my slightly
Brian Dean said:
I'm using a dual 350MHz Dell Precision 410 with 4.0-19990130-SNAP (SMP
enabled) to prototype a program that uses asynchronous read and write
(aio_read() and aio_write()), and found that the following simple and
not very useful program (it's for demonstration purposes only!)
Richard Seaman, Jr. said:
As I indicated to you several weeks ago, I think it is possible to have
a priority inversion problem in spinlocks that spin on sched_yield.
The yield call, as implemented, partly addresses the issue. However,
as you commented to me, it does so poorly.
If the
Matthew Dillon said:
:Matt,
:
:Does datasize limit the number of backed pages, or the amount of address
:space used by a process? I.e., can I grow myself a large chunk of address
:space using mmap to the same region of a file, and then read into that
:large chunk (presumably larger than the
Dan Root said:
Content-Description: Mail message
Is this normal, or should I look for some process that's thrashing through
vast amounts of pages in short periods of time?
It is normal and expected. A little secret about FreeBSD's VM is that
it works on a page demand type timeclock and not
41 matches
Mail list logo
