Andrea Arcangeli [EMAIL PROTECTED] writes:
On Wed, Jan 10, 2001 at 11:46:03AM +, David Woodhouse wrote:
So the VM code spends a fair amount of time scanning lists of pages which
it really can't do anything about?
Yes.
Would it be possible to put such pages on different list, so
Ralf Baechle [EMAIL PROTECTED] writes:
On Thu, Jan 11, 2001 at 12:56:57AM +0100, David Weinehall wrote:
The MMU on these systems is a CAM, and the mmu table is thus backwards to
convention. (It also means you can notionally map two physical addresses to
one virtual but thats
Ralf Baechle [EMAIL PROTECTED] writes:
On Fri, Jan 12, 2001 at 09:11:43PM +, Russell King wrote:
Eric W. Biederman writes:
Hmm. I would think that increasing the logical page size in the kernel
would be the trivial way to handle virtual aliases. (i.e.) with a large
enough
Ralf Baechle [EMAIL PROTECTED] writes:
On Fri, Jan 12, 2001 at 09:10:54AM -0700, Eric W. Biederman wrote:
Having a reverse mappings is the least sucky way to handle virtual aliases
of certain types of MIPS caches.
Hmm. I would think that increasing the logical page size
Ralf Baechle [EMAIL PROTECTED] writes:
On Mon, Jan 15, 2001 at 01:41:06AM -0700, Eric W. Biederman wrote:
(Cc list truncated since probably not so many people do care ...)
shared mmap. This is the important one. Since we have a logical
backing store this is easy to handle. We just
Anton Blanchard [EMAIL PROTECTED] writes:
At least for sparc it's already supported. Right now I don't feel like
looking into the 2.4 solution but checkout srmmu_vac_update_mmu_cache in
the 2.2 kernel.
I killed that hack now that we align all shared mmaps to the same virtual
Anton Blanchard [EMAIL PROTECTED] writes:
Hi,
Where do you do this? And how do you handle the case of aliases with kseg,
the giant kernel mapping.
Aliases between user and kernel mappings of a page are handled by
flush_page_to_ram the old interface) or {copy,clear}_user_page,
Werner Almesberger [EMAIL PROTECTED] writes:
I agree writing the code to understand the table may be a significant
issue. On the other hand I still think it is worth a look, being
able to unify option parsing for multiple platforms is not a small
gain, nor is getting out from short
David Wragg [EMAIL PROTECTED] writes:
While testing some kernel code of mine on a machine with
CONFIG_HIGHMEM enabled, I've run into the limit on the number of pages
that can be kmapped at once. I was surprised to find it was so low --
only 2MB/4MB of address space for kmap (according to
David Wragg [EMAIL PROTECTED] writes:
I'd still like to know what the basis for the current kmap limit
setting is.
Mostly at one point kmap_atomic was all there was. It was only the
difficulty of implementing copy_from_user with kmap_atomic that convinced
people we needed something more. So
Marcelo Tosatti [EMAIL PROTECTED] writes:
On Wed, 31 Jan 2001, Stephen C. Tweedie wrote:
Hi,
On Wed, Jan 31, 2001 at 01:05:02AM -0200, Marcelo Tosatti wrote:
However, the pages which are contiguous on swap are not necessarily
contiguous in the virtual memory area where the
David Gould [EMAIL PROTECTED] writes:
Hmmm, arguably reading pages we do not want is a mistake. I should think that
if a big performance win is required to justify a design choice, it should
be especially required to show such a win for doing something that on its
face is wrong.
The case
Jamie Lokier [EMAIL PROTECTED] writes:
Richard B. Johnson wrote:
However, PCI to memory copying runs at about 300 megabytes per
second on modern PCs and memory to memory copying runs at over 1,000
megabytes per second. In the future, these speeds will increase.
That would be big
Maciej W. Rozycki [EMAIL PROTECTED] writes:
On 4 May 2001, Eric W. Biederman wrote:
The example that sticks out in my head is we rely on the MP table to
tell us if the local apic is in pic_mode or in virtual wire mode.
When all we really have to do is ask it.
You can't. IMCR
H . J . Lu [EMAIL PROTECTED] writes:
On Fri, May 11, 2001 at 04:28:05PM -0700, David S. Miller wrote:
H . J . Lu writes:
2.4.4-ac8 disables IP auto config by default even if CONFIG_IP_PNP is
defined. Here is a patch.
It doesn't make any sense to enable this unless parameters
Daniel Phillips [EMAIL PROTECTED] writes:
On Tuesday 15 May 2001 23:20, Nicolas Pitre wrote:
Personally, I'd really like to see /dev/ttyS0 be the first detected
serial port on a system, /dev/ttyS1 the second, etc.
There are well-defined rules for the first four on PC's. The ttySx
H . J . Lu [EMAIL PROTECTED] writes:
On Sun, May 13, 2001 at 01:24:18PM -0600, Eric W. Biederman wrote:
H . J . Lu [EMAIL PROTECTED] writes:
It doesn't make any senses. When I specify CONFIG_IP_PNP and
BOOTP/DHCP, I want a kernel with IP config using BOOTP/DHCP. I would
expect IP
Jonathan Lundell [EMAIL PROTECTED] writes:
At 10:42 AM +0200 2001-05-19, Kai Henningsen wrote:
Jeff Garzik's ethtool
extension at least tells me the PCI bus/dev/fcn, though, and from
that I can write a userland mapping function to the physical
location.
I don't see how PCI
Ben LaHaise [EMAIL PROTECTED] writes:
Hey folks,
The work-in-progress patch for-demonstration-purposes-only below consists
of 3 major components, and is meant to start discussion about the future
direction of device naming and its interaction block layer. The main
motivations here are
H . J . Lu [EMAIL PROTECTED] writes:
It doesn't make any senses. When I specify CONFIG_IP_PNP and
BOOTP/DHCP, I want a kernel with IP config using BOOTP/DHCP. I would
expect IP config is turned for BOOTP/DHCP by default. You can turn
it off by passing ip=off to kernel. Did I miss something?
David Woodhouse [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] said:
There wasn't even DHCP support before so yes you did. As you can't
get the nfs mount point from bootp.
Wasn't there a default? The Indy behind me seems to try to mount
/tftpboot/172.16.18.195, so I put a filesystem
Stephen C. Tweedie [EMAIL PROTECTED] writes:
Hi,
On Wed, May 23, 2001 at 01:01:56PM -0700, Linus Torvalds wrote:
On Wed, 23 May 2001, Stephen C. Tweedie wrote:
that the filesystems already do. And you can do it a lot _better_ than the
current buffer-cache-based approach. Done
Linus Torvalds [EMAIL PROTECTED] writes:
On 25 May 2001, Eric W. Biederman wrote:
For the small random read case we could use a
mapping-a_ops-readpartialpage
No, if so I'd prefer to just change readpage() to take the same kinds of
arguments commit_page() does, namely the beginning
"Heusden, Folkert van" [EMAIL PROTECTED] writes:
Hi,
ADC why not
ADC #include arch/i386/etc.h
ADC Amit
Since that is not cross-platform. I like a solution which does the #include
transparantly
for alpha/i386/etc.
Umm. Then the include file should probably rest under the include
Rik van Riel [EMAIL PROTECTED] writes:
On Wed, 21 Mar 2001, Patrick O'Rourke wrote:
Since the system will panic if the init process is chosen by
the OOM killer, the following patch prevents select_bad_process()
from picking init.
One question ... has the OOM killer ever selected init
Guest section DW [EMAIL PROTECTED] writes:
On Wed, Mar 21, 2001 at 08:48:54PM -0300, Rik van Riel wrote:
On Wed, 21 Mar 2001, Patrick O'Rourke wrote:
Since the system will panic if the init process is chosen by
the OOM killer, the following patch prevents select_bad_process()
from
I have recently developed a patch that allows linux to directly boot
into another linux kernel. With the code freeze it appears
inappropriate to submit it at this time.
Linus in principal do you have any trouble with this kind of
functionality?
The immediate applications of this code, are:
"Stephen Gutknecht (linux-kernel)" [EMAIL PROTECTED] writes:
A Linux Kernel compile test does a really good job of testing the hard disk,
RAM, and CPU... as it executes all types of instructions and the final
output depends on all prior steps completing correctly. On a really fast
system (
Aaron Sethman [EMAIL PROTECTED] writes:
You might want to take a look at using reiserfs on the 130GB partition, as
its is journalled and doesn't need to be fsck'ed.
No.
All journaling filesystems need to be fsck'ed.
A correctly operating one simply doesn't need to be fsck'ed because
of
Peter Samuelson [EMAIL PROTECTED] writes:
[Matt D. Robinson]
Any way we can standardize 'make install' in the kernel? It's
disturbing to have different install mechanisms per platform ...
I can make the changes for a few platforms.
2.5 material, already on the todo list.
What is the
Ronald G Minnich [EMAIL PROTECTED] writes:
On Fri, 24 Nov 2000, I+D wrote:
I'm trying to boot an AMD Elan520 board without bios
with kernel 2.4.0-test10 configured for i486 and PCI direct access.
This kernel boots correctly from HD using the bios provided with the
evaluation board
Alan Cox [EMAIL PROTECTED] writes:
benn compiled into the kernel, and not as a module) always gave the
errors:
eth0: Transmit timed out: status 0050 0090 at 134704418/134704432
eth0: Trying to restart the transmitter...
Known problem. This one might be fixed in current 2.2.18pre.
...
Ron. vger.rutgers.edu died a couple of months ago.
vger.kernel.org is the new machine, the linux kernel mailing list is on.
I'm forwarding this there. I don't know how much help we can
get on a bug report against 2.4.0-test6 though.
Eric
ron
On 30 Nov 2000, Eric W. Biederman wrote:
Ronald
"Jeff V. Merkey" [EMAIL PROTECTED] writes:
Cool. ORACLE is going to **SMOKE** on EXT2 with this change.
Pessimism
Hmm I don't see how ORACLE is going to **SMOKE**.
Last I looked ORACLE would need a query optimizer that always
would find the best possible index and much less overhead to
Linus Torvalds [EMAIL PROTECTED] writes:
In short, I don't see _those_ kinds of issues. I do see error reporting as
a major issue, though. If we need to do proper low-level block allocation
in order to get correct ENOSPC handling, then the win from doing deferred
writes is not very big.
To
Linus Torvalds [EMAIL PROTECTED] writes:
On 30 Dec 2000, Eric W. Biederman wrote:
One other thing to think about for the VFS/MM layer is limiting the
total number of dirty pages in the system (to what disk pressure shows
the disk can handle), to keep system performance smooth when
Kai Germaschewski [EMAIL PROTECTED] writes:
On Tue, 2 Jan 2001, Gerold Jury wrote:
I have reversed the patches part by part, the only thing that makes a
difference is the diversion services.
The reason for this remains unknown for me.
I think I found it. Could everybody who was
Russell King [EMAIL PROTECTED] writes:
Kai Germaschewski writes:
The patch is right, the explanation was wrong. Sorry, I didn't CC l-k when
I found what was really going on. Other source files used a global
initialized variable "divert_if" as well, so this became the same one as
the one
Chris Wedgwood [EMAIL PROTECTED] writes:
On Sat, Jan 06, 2001 at 03:58:20PM +, Alan Cox wrote:
Ext2 handles large files almost properly. (properly on 2.2 +
patches) NFSv3 handles large files but might be missing the
O_LARGEFILE check. I believe reiserfs went to at least
Rik van Riel [EMAIL PROTECTED] writes:
The following bugs _could_ be fixed ... I'm not 100% certain
but they're probably gone (could somebody confirm/deny?):
* mm-rss is modified in some places without holding the
page_table_lock
As of linux-2.4.0-test13-pre7 I can confirm that this
Alan Cox [EMAIL PROTECTED] writes:
Putting the LFS checks, max filesize checks into the VFS sounds
right for 2.4.x because it fixes lots of filesystems, with just a
couple of lines of code.
Rather more than that, and it only fixes those using generic_file_*
True. But it is
Rik van Riel [EMAIL PROTECTED] writes:
On Sun, 7 Jan 2001, Linus Torvalds wrote:
On Sun, 7 Jan 2001, Alan Cox wrote:
-ac has the rather extended ramfs with resource limits and stuff. That one
also has rather more extended bugs 8). AFAIK none of those are in the
vanilla
ramfs
Linus Torvalds [EMAIL PROTECTED] writes:
On Sun, 7 Jan 2001, Albert Cranford wrote:
Could anybody with a VIA chip who has the energy please do something for
me:
- enable DEBUG in arch/i386/kernel/pci-i386.h
- do a "/sbin/lspci -xxvvv" on the interrupt routing chip (it's the
Zlatko Calusic [EMAIL PROTECTED] writes:
Yes, but a lot more data on the swap also means degraded performance,
because the disk head has to seek around in the much bigger area. Are
you sure this is all OK?
I don't think we have more data on the swap, just more data has an
allocated home on
Linus Torvalds [EMAIL PROTECTED] writes:
On 8 Jan 2001, Eric W. Biederman wrote:
Zlatko Calusic [EMAIL PROTECTED] writes:
Yes, but a lot more data on the swap also means degraded performance,
because the disk head has to seek around in the much bigger area. Are
you sure
Dan Kegel [EMAIL PROTECTED] writes:
It's harder to write correct programs that use edge-triggered events.
Huh? The race between when an event is reported, and when you take action
on it effectively means all events are edge triggered.
So making the interface clearly edge triggered seems to
"David S. Miller" [EMAIL PROTECTED] writes:
Date: Tue, 24 Oct 2000 13:50:10 -0700 (PDT)
From: Linus Torvalds [EMAIL PROTECTED]
Does the above make it work for you? I don't know if PCI even has
the notion of transparent bridging, and quite frankly I doubt it
does. The
Raul Miller [EMAIL PROTECTED] writes:
Can anyone tell me about the viability of a guarantee_memory() syscall?
[I'm thinking: it would either kill the process, or allocate all virtual
memory needed for its shared libraries, buffers, allocated memory, etc.
Furthermore, it would render this
Joe [EMAIL PROTECTED] writes:
I remember hearing about various debates about the /proc structure. I
was wondering if anyone had ever considered storing some of the data in
xml format rather than its current format? Things like /proc/meminfo
and cpuinfo may work good in this format as then
Ion Badulescu [EMAIL PROTECTED] writes:
On Sun, 5 Nov 2000 23:42:25 +0100, Marc Lehmann [EMAIL PROTECTED] wrote:
On Sun, Nov 05, 2000 at 04:06:37PM -0500, Jakub Jelinek [EMAIL PROTECTED]
wrote:
for SGI, or SGI would have to be willing to assign some code to FSF.
Which is the
David Woodhouse [EMAIL PROTECTED] writes:
The current situation is equivalent to stopping forwarding packets each
time an app on the local machine decides it wants to send its own packets,
after a period of inactivity.
Defaulting to zero on boot is fine. Defaulting to zero after the module
Horst von Brand [EMAIL PROTECTED] writes:
I'd prefer to be a guinea pig for one of 3 or 4 generic kernels distributed
in binary than of one of the hundreds of possibilities of patching a kernel
together at boot, plus the (presumamby rather complex and fragile)
machinery to do so *before* the
Andrew Morton [EMAIL PROTECTED] writes:
George Anzinger wrote:
The notion of releasing a spin lock by initializing it seems IMHO, on
the face of it, way off. Firstly the protected area is no longer
protected which could lead to undefined errors/ crashes and secondly,
any future use
Michael Rothwell [EMAIL PROTECTED] writes:
"Eric W. Biederman" wrote:
I have recently developed a patch that allows linux to directly boot
into another linux kernel.
This would rock. One place I can think of using it is with distro
installers. The installer boots a ge
"H. Peter Anvin" [EMAIL PROTECTED] writes:
Followup to: [EMAIL PROTECTED]
By author:[EMAIL PROTECTED] (Eric W. Biederman)
In newsgroup: linux.dev.kernel
The interface is designed to be simple and inflexible yet very
powerful. To that end the code just takes an
Adam Lazur [EMAIL PROTECTED] writes:
Eric W. Biederman ([EMAIL PROTECTED]) said:
Michael Rothwell [EMAIL PROTECTED] writes:
This would rock. One place I can think of using it is with distro
installers. The installer boots a generic i386 kernel, and then installs
an optimized (i.e
Adam Lazur [EMAIL PROTECTED] writes:
Eric W. Biederman ([EMAIL PROTECTED]) said:
I have recently developed a patch that allows linux to directly boot
into another linux kernel. With the code freeze it appears
inappropriate to submit it at this time.
Aside from what looks
"H. Peter Anvin" [EMAIL PROTECTED] writes:
"Eric W. Biederman" wrote:
Hmm. You must mean similiar to milo.
Have fun. With linuxBIOS I'm working exactly the other way. Killing
off the BIOS. And letting the initial firmware be just a boot loader.
The red
Andrea Arcangeli [EMAIL PROTECTED] writes:
On Sun, Nov 12, 2000 at 06:14:36AM -0700, Eric W. Biederman wrote:
x86-64 doesn't load the segment registers at all before use.
Yes, before switching to 64bit long mode we never do any data access. We do a
stack access to clear eflags only while
Andrea Arcangeli [EMAIL PROTECTED] writes:
On Sun, Nov 12, 2000 at 06:14:36AM -0700, Eric W. Biederman wrote:
x86-64 doesn't load the segment registers at all before use.
Yes, before switching to 64bit long mode we never do any data access. We do a
stack access to clear eflags only while
Erik Andersen [EMAIL PROTECTED] writes:
On Thu Nov 09, 2000 at 01:18:24AM -0700, Eric W. Biederman wrote:
I have recently developed a patch that allows linux to directly boot
into another linux kernel.
Looks very cool. I'm curious about your decision to use ELF images. This
makes
Erik Andersen [EMAIL PROTECTED] writes:
On Tue Nov 14, 2000 at 07:59:18AM -0700, Eric W. Biederman wrote:
All mkelfImage does is the pasting of initrd's, command lines,
and just a touch of argument conversion code.
You can link in an initrd using linker magic, i.e.
$(OBJCOPY
Juan [EMAIL PROTECTED] writes:
Alexander Viro escribió:
On Tue, 14 Nov 2000, Juan wrote:
Hi!.
Is there any patch or project to address logically the buffer cache?.
Now, you use three parameters to find a buffer in cache: device, block
number, and block size. But, what
Rik van Riel [EMAIL PROTECTED] writes:
On Wed, 15 Nov 2000, Andreas Osterburg wrote:
Because I set up a diskless Linux-workstation, I want to swap
over NFS. For this purpose I found only patches for "older"
Linux-versions (2.0, 2.1, 2.2?).
Does anyone know wheter there are patches
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
There are a couple of differences.
But the big one is I'm trying to do it right.
So why do you need a file-based interface then ? ;-)
When possible it is nice to set as much policy as possible,
without removing
:15AM -0700, Eric W. Biederman wrote:
I can tell you don't have real hardware. The non obviousness
I need to retract this a bit. You are still building a compressed image,
and the code in the boot/compressed/head.S remains unchanged and loads
segment registers, so it works by luck
Daniel Phillips [EMAIL PROTECTED] writes:
Actually, I was planning on doing on putting in a hack to do something
like that: calculate a checksum after every buffer data update and check
it after write completion, to make sure nothing scribbled in the buffer
in the interim. This would also
Werner Almesberger [EMAIL PROTECTED] writes:
Rik van Riel wrote:
Did you try to load an initrd on a low-memory machine?
It shouldn't work and it probably won't ;)
You must be really low on memory ;-)
# zcat initrd.gz | wc -c
409600
(ash, pwd, chroot, pivot_root, smount, and still
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
I have one that loads a second kernel over the network using dhcp
to configure it's interface and tftp to fetch the image and boots
that is only 20kb uncompressed
Neat ;-) My goal is actually not only size
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
Well there is that. Somehow implementing scatter/gather from
a user space process seemed like a potential mess, and extra work.
Did you look at kiobufs ? I think they may just have the right
functionality. I always
David Ford [EMAIL PROTECTED] writes:
Andrew Park wrote:
I get a message
neighbour table overflow
What does that mean? It seems that
net/ipv4/route.c
is the place where it prints this. But under what circumstances
does this happen?
Thanks
It means you
Werner Almesberger [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
The code wasn't trivially reusable, and the structures had a lot
of overhead.
There's some overhead, but I think it's not too bad. I'll give it a
try ...
The rebooting is done the rest is not yet.
Ah, and I
Miles Lane [EMAIL PROTECTED] writes:
http://www.osdn.com/conferences/kernel/
Thanks to all responsible for getting these captures
of the Kernel 2.5 Workshop prosentations put together.
There is one major shortcoming of the recordings.
Usually, only the comments of the
A little while ago I was playing with building an elf self extracting
binary. In doing so I discovered that the linux kernel does not
handle elf program headers with multiple BSS segments.
Eric
Binary files linux-2.2.19/drivers/char/conmakehash and
A little while ago I was playing with building an elf self extracting
binary. In doing so I discovered that the linux kernel does not
handle elf program headers with multiple BSS segments.
In building a patch for 2.4.3 I also discovered that we are not taking
the mmap_sem around do_brk in the
Here is a forward port of the 2.2.x improvements to ipconfig.c.
Especially support for DHCP.
Eric
diff -uNr linux-2.4.3/Documentation/Configure.help linux-2.4.3.ipdhcp/Documentation/Configure.help
--- linux-2.4.3/Documentation/Configure.help Fri Apr 20 12:06:37 2001
+++
David S. Miller [EMAIL PROTECTED] writes:
Eric W. Biederman writes:
In building a patch for 2.4.3 I also discovered that we are not taking
the mmap_sem around do_brk in the exec paths.
Does that really matter?
In the library loader I can certainly see it making a difference.
Who
David S. Miller [EMAIL PROTECTED] writes:
Eric W. Biederman writes:
In building a patch for 2.4.3 I also discovered that we are not taking
the mmap_sem around do_brk in the exec paths.
Does that really matter? Who else can get at the address space? We
are a singly referenced
Linus Torvalds [EMAIL PROTECTED] writes:
On 23 Apr 2001, Eric W. Biederman wrote:
ptrace is protected by the big kernel lock, but exec isn't so that
doesn't help. Hmm. ptrace does require that the process be stopped
in all cases
Right. Ptrace definitely cannot access a process
Manfred Spraul [EMAIL PROTECTED] writes:
Well looking a little more closely than I did last night it looks like
access_process_vm (called from ptrace) can cause what amounts to a
page fault at pretty arbitrary times.
It's also used for several /proc/pid files.
I remember that I got
Jeff Garzik [EMAIL PROTECTED] writes:
Andres Salomon wrote:
This is what I was told (it was only needed for secondary video
devices). From that, I would expect that all video devices would
need it, just in case they happened to be the second card. Am I
missing some subtlety in some of
Do you know if anyone has fixed the lazy vmalloc code? I know of
as of early 2.4 it was broken on alpha. At the time I noticed it I didn't
have time to persue it, but before I forget to even put in a bug
report I thought I'd ask if you know anything about it?
Eric
-
To unsubscribe from this
Andrea Arcangeli [EMAIL PROTECTED] writes:
On Sun, Apr 29, 2001 at 05:27:10PM -0600, Eric W. Biederman wrote:
Do you know if anyone has fixed the lazy vmalloc code? I know of
as of early 2.4 it was broken on alpha. At the time I noticed it I didn't
have time to persue it, but before
Steffen Persvold [EMAIL PROTECTED] writes:
[EMAIL PROTECTED] wrote:
On Sun, 29 Apr 2001, Steffen Persvold wrote:
I've learned it the hard way, I have two types : Compaq DL360 (rev 5) and a
Tyan S2510 (rev 6). On the compaq machine I constantly get data corruption
on
the last
Alex Huang [EMAIL PROTECTED] writes:
Dear All,
How can do to disable the L1 cache in linux ?
Are there some commands or directives to disable it ??
Play with the MTRR's and disable caching on memory.
Stupid but it should get what you want.
Eric
-
To unsubscribe from this list: send the
Fabrice Gautier [EMAIL PROTECTED] writes:
On Wed, 02 May 2001 11:54:11 +0200
Reto Baettig [EMAIL PROTECTED] wrote:
Hi
I just installed 2.4.4 on our alpha SMP boxes (ES40) and now I have
problems with the serial console:
I get same kind of problem when upgrading from 2.4.2 to
Fabrice Gautier [EMAIL PROTECTED] writes:
On 02 May 2001 10:37:21 -0600
[EMAIL PROTECTED] (Eric W. Biederman) wrote:
Fabrice Gautier [EMAIL PROTECTED] writes:
So this this probably a sulogin/mingetty problem. They should set the
CREAD flag in your tty c_cflag.
the patch
Alan Cox [EMAIL PROTECTED] writes:
I suspect it would be safe to round up to the next megabyte, possibly up
to 64MB or so. But much more would make me nervous.
Any suggestions?
I'd go for 1MByte simply because I've not seen an EBDA/NVRAM area that large
stuck at the top of RAM. 1Mb
Matt D. Robinson [EMAIL PROTECTED] writes:
It looks like around 2.3.30 or so, someone added the call
disable_local_APIC() to smp_send_stop(). I'm not sure what the
intention was, but I'm getting some strange behavior as a result
based on some code I'm writing.
Basically, I'm doing the
Alan Cox [EMAIL PROTECTED] writes:
There are a couple of options here.
1) read the MTRRs unless the BIOS is braindead it will set up that area as
write-back. At any rate we shouldn't ever try to allocate a pci region
that is write-back cached.
'unless the BIOS is braindead'.
Alan Cox [EMAIL PROTECTED] writes:
Seriously. With the general attitude of distrusting BIOS's I have
been amazed at the number of things linux expects the BIOS to get
right. In practice windows seem to trust the BIOS much less than
linux does.
It becomes more and more obvious over
Matt D. Robinson [EMAIL PROTECTED] writes:
It's an SMP (and only when your system crashes on a CPU other
than 0) problem. I did some more checking of this to verify the
specifics of the behavior. Thanks for the sarcasm, though. :)
O.k. That makes perfect sense then. See below.
All I
Jeffrey W. Baker [EMAIL PROTECTED] writes:
On Tue, 5 Jun 2001, Derek Glidden wrote:
After reading the messages to this list for the last couple of weeks and
playing around on my machine, I'm convinced that the VM system in 2.4 is
still severely broken.
This isn't trying to test
Andrew Morton [EMAIL PROTECTED] writes:
Jeffrey W. Baker wrote:
Because the 2.4 VM is so broken, and
because my machines are frequently deeply swapped,
The swapoff algorithms in 2.2 and 2.4 are basically identical.
The problem *appears* worse in 2.4 because it uses lots
more swap.
Derek Glidden [EMAIL PROTECTED] writes:
John Alvord wrote:
On Wed, 06 Jun 2001 11:31:28 -0400, Derek Glidden
[EMAIL PROTECTED] wrote:
I'm beginning to be amazed at the Linux VM hackers' attitudes regarding
this problem. I expect this sort of behaviour from academics - ignoring
Jeff Garzik [EMAIL PROTECTED] writes:
I'm sorry but this is a regression, plain and simple.
Previous versons of Linux have worked great on diskless workstations
with NO swap.
Swap is extra space to be used if we have it and nothing else.
Given the slow speed of disks to use them
Derek Glidden [EMAIL PROTECTED] writes:
The problem I reported is not that 2.4 uses huge amounts of swap but
that trying to recover that swap off of disk under 2.4 can leave the
machine in an entirely unresponsive state, while 2.2 handles identical
situations gracefully.
The
Mike Galbraith [EMAIL PROTECTED] writes:
On 6 Jun 2001, Eric W. Biederman wrote:
Derek Glidden [EMAIL PROTECTED] writes:
The problem I reported is not that 2.4 uses huge amounts of swap but
that trying to recover that swap off of disk under 2.4 can leave the
machine
LA Walsh [EMAIL PROTECTED] writes:
Eric W. Biederman wrote:
The hard rule will always be that to cover all pathological cases swap
must be greater than RAM. Because in the worse case all RAM will be
in thes swap cache. That this is more than just the worse case in 2.4
is problematic
[EMAIL PROTECTED] (Linus Torvalds) writes:
Somebody interested in trying the above add? And looking for other more
obvious bandaid fixes. It won't fix swapoff per se, but it might make
it bearable and bring it to the 2.2.x levels.
At little bit. The one really bad behavior of not letting
1 - 100 of 10702 matches
Mail list logo
