On Mon, Sep 11, 2000 at 05:08:22PM +0100, Alan Cox wrote:
The very fact that a large and important patch by
(as far as I can see) the NFS _maintainers_ is not
being accepted by the stable kernel maintainer does
not fill one with hope about the quality of the patch.
The current patch
On Tue, Sep 12, 2000 at 01:41:45AM -0500, Oliver Xymoron wrote:
This is similar to my patch-names patch, which lets you add components
to uname too. IIRC, it was rejected because it made things easier.
Erm? Not really. Not unless you want
On 2000-09-11 09:22:23 -0400, Chris Mason wrote:
Thanks Andrea, Andi, new patch is attached, with the warning messages
removed. The first patch got munged somewhere between test machine and
mailer, please don't use it.
I've been hammering this all day installing the relevent tools and
On Tue, 12 Sep 2000, Matthew Hawkins wrote:
Very stable so far, and having Andrea's VM patches in (I usually
didn't put them in) has made a noticeable difference - xmms has
rarely skipped and things start faster and run smoother.
Hopefully I'll see the same (or better) results from Rik's
Rik van Riel wrote:
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Wed, 6 Sep 2000, George Anzinger wrote:
The times a kernel is not preemptable under this patch are:
While handling interrupts.
While doing "bottom half" processing.
While holding a spinlock, writelock or
According to Ion Badulescu:
In article 8pjlk6$vnf$[EMAIL PROTECTED] you wrote:
However, ^C does not stop anything. No signal gets sent to anybody.
I don't want to make it too large because it won't fit on a floppy
if I do.
That means you don't have a controlling tty.
But why is
I know about sar which can deliver what I want for disks and/or
partitions. What about if I want to know how much I/O is caused by
userspace programs?
Looking at the proc-interface in 2.2.xx the necessary bits aren't
available. The BSD process accounting doesn't provide them either, the
I/O
On Tue, 12 Sep 2000, Miquel van Smoorenburg wrote:
It is a tty, it's just that if you open(2) it, it doesn't become
your _controlling_ tty by default. See drivers/char/tty_io.c (I
think, that's from the top of my head).
Then I guess the kernel doesn't perform the proper setup when it opens
Hi, I have the following machine
http://www.intel.com/isp/servers/lb440gx.htm
with Dual P3 550's and 2GB of RAM in them. Redhat 6.2 with its stock
kernel 2.2.14-5 detects the 2GB of RAM and boots up happily.
When I compile 2.2.17 with 2GB RAM, I get the following error on boot
up
"Jamie" == Jamie Lokier [EMAIL PROTECTED] writes:
Jamie According to group legend here (I wasn't around but will repeat
Jamie what I was told), we spent about 1 year trying to get docs on
Jamie Intel's i960 based gigabit card so we could program it.
Jamie Eventually we gave up and moved to
David Woodhouse [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] said:
The best solution is to have a stub which is always resident that
does the inc/dec of the module count. This stub can reserve the
syscall number as well.
_Please_ don't have a stub in the kernel which is conditionally
[EMAIL PROTECTED] said:
I have to admit, the thought hadn't occurred to me to do that. It
almost sounds like a good idea... after all the stub can't be used if
no modules can be loaded. Are you thinking, then, that the stub can't
be used by compiled in (ie non-module) code? Or am I
"Keith" == Keith Owens [EMAIL PROTECTED] writes:
Keith On Wed, 6 Sep 2000 21:49:44 +0100 (BST), Alan Cox
Keith [EMAIL PROTECTED] wrote:
Use a different gcc. There are reasons people shipping 2.96 for
intel x86 also include egcs. The kernel isnt ready for 2.96
Keith Out of curiousity, which
Hi,
A two processor SMP machine has been crashing recently, sometimes it
manages to Oops before hand. Below is the klogd output with assembly
from gdb. The do_generic_file_read+347 Oops occurred once, the dput+77
Oops has occurred five times; all five are below.
Does anyone recognise
Jes Sorensen wrote:
It took me a little while in the beginning to convince Alteon to open
up and provide docs, but since they saw the light they have been
extremely helpful and went much further in their openness than I had
ever expected or dared to hope for.
And now it's really showing in
"Horst" == Horst von Brand [EMAIL PROTECTED] writes:
Horst "Albert D. Cahalan" [EMAIL PROTECTED] said: [...]
That would be the "H=F8jland" in your .sig, right? No problem, '='
is a standard character.
My MUA has been RFC-compliant since before this "MIME" thing
existed, so I can see the
Hi,
Yesterday I tried to install 2.2.17 on a pentium-mmx. Nothing fancy; 3c509,
3c905B, ide disk+cdrom, 32MB ram.
2.0.38 runs fine.
system crashes (hangs) after it decompressed the kernel, after the "Now
booting the kernel"-message.
I tried both an bzImage and the zImage.
Couldn't find anything
C program instructions are in ASCII, data certainly isn't restricted to that.
If you or your M*A can't or won't deal with anything but plain text, then
filter it. Plain text is clearly in the minority of emails throughout the
world and the people on LKML seem in general not to care about MIME
On Tue, 12 Sep 2000 10:25:16 +0100,
David Woodhouse [EMAIL PROTECTED] wrote:
Unless it's _absolutely_ necessary, the kernel image (i.e. vmlinux) should
not contain any code which is dependent on CONFIG_*_MODULE options.
Therefore, stuff like...
#ifdef CONFIG_WIN32_MODULE
On Tue, 12 Sep 2000 10:29:09 +0100,
Malcolm Beattie [EMAIL PROTECTED] wrote:
To initialise the system call and suchlike traps,
arch/i386/kernel/traps.c does
set_system_gate(3,int3); /* int3-5 can be called from all */
set_system_gate(4,overflow);
Normal users are only able to create a SIGIO signal when connecting.
That's very unlikely. TCP does not propagate gid/uid information over sockets,
not even over localhost.
However if something is looking at current- and the test is on localhost
then it starts to become quite believable
-
In article [EMAIL PROTECTED] you wrote:
Hi,
Yesterday I tried to install 2.2.17 on a pentium-mmx. Nothing fancy; 3c509,
[snip]
What should I do as the next problem-determinationstep?
Check if you didn't accidentally build a Pentium Pro/II kernel
(see the .config file, or with "make
In article [EMAIL PROTECTED] you wrote:
#ifdef CONFIG_MODULES
EXPORT_SYMBOL(dynamic_syscall_in_modules_helper);
#endif
I think this is total bullshit. EXPORT_SYMBOLS should be a nop anyway if
modules are turned off, as there is no use for it.
Greetings,
Arjan van de Ven
-
To
oFix illegal use of section attributes (Arjan van de Ven)
Which bit of the patch is this? Nothing changes any section
Removes some __initdata and similar tags from externs
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
On 12 Sep 00 at 21:25, Keith Owens wrote:
0x85) vanish after the system has booted further. printk shows that
idt_table is correctly updated immediately after the set_system_gate
but once the system has booted the entries for my new traps have
reverted. (printk telemetry available on
On Tue, 12 Sep 2000, David Ford wrote:
C program instructions are in ASCII, data certainly isn't restricted to that.
If you or your M*A can't or won't deal with anything but plain text, then
filter it. Plain text is clearly in the minority of emails throughout the
world and the people on
On Tue, 12 Sep 2000 12:40:45 +0200 (CEST),
[EMAIL PROTECTED] (Arjan van de Ven) wrote:
In article [EMAIL PROTECTED] you wrote:
#ifdef CONFIG_MODULES
EXPORT_SYMBOL(dynamic_syscall_in_modules_helper);
#endif
I think this is total bullshit. EXPORT_SYMBOLS should be a nop anyway if
modules are
Hi,
last night I made a few new patches. For one there's a
quick scheduler patch which makes the scheduler consider
CPU usage on a somewhat longer term as well as on the
short term, giving CPU time away a bit more fairly when
a process sleeps for a few timeslices.
The second patch is a new
with Dual P3 550's and 2GB of RAM in them. Redhat 6.2 with its stock
kernel 2.2.14-5 detects the 2GB of RAM and boots up happily.
When I compile 2.2.17 with 2GB RAM, I get the following error on boot
up
You probably want to get the 'bigmem' patches
request_module[block-major-8]: Rootfs
On Mon, 11 Sep 2000, Jeff Garzik wrote:
I hear that the new NFS patch is "better and more stable" etc. but no
details.
hard to give details as i havn't used unpatched linux 2.2 nfs in a
very long time. best evidence from me is anecdotal: linux 2.4 / 2.2
nfs patches works perfectly for me
Jes Sorensen wrote:
It took me a little while in the beginning to convince Alteon to open
up and provide docs, but since they saw the light they have been
extremely helpful and went much further in their openness than I had
ever expected or dared to hope for.
And now it's really
Hi Dan!
With your patch test8 compiles but I get no sound. The chip is not
recognized during bootup (I have sound compiled in, not as a module). With
2.2.18pre2 it works well...
Thanx anyway,
Bernd
PS: If you need someone to test patches for this chip I'll do it.
On Mon, Sep 11,
Hi!
While version 2.1 works OK, v2.3 some more cleanups and enhancements
to the driver. These are:
* Added VIA clone chipsets to the comments at the beginning of the file.
* Simpler VIA southbridge detection using a table only now, two version
specific kludges removed.
* Removed 8-bit
David Woodhouse [EMAIL PROTECTED] wrote:
Unless it's _absolutely_ necessary, the kernel image (i.e. vmlinux) should
not contain any code which is dependent on CONFIG_*_MODULE options.
Therefore, stuff like...
#ifdef CONFIG_WIN32_MODULE
EXPORT_SYMBOL(my_win32_helper_func);
#endif
Jes Sorensen wrote:
It took me a little while in the beginning to convince Alteon to open
up and provide docs, but since they saw the light they have been
extremely helpful and went much further in their openness than I had
ever expected or dared to hope for.
And now it's
Hi,
"kuznet" == kuznet [EMAIL PROTECTED] writes:
kuznet Hello!
kuznet In input path you have a packet. Add it to backlog and
kuznet processing will be resumed after lock is released. Compare
kuznet with tcp.
serializing the kick. Well, maybe my solution could still be
On Tue, 12 Sep 2000, David Howells wrote:
I think now that I'm probably best providing a generic pluggable syscall
handler, one that is very careful to make sure the syscall can't be entered
whilst the module is being unloaded.
Whats the problem with just not allowing the module to
I was just about to send an identical email. Do we have a quick fix to
remedy this? (config file available upon request of course)
On Tue, Sep 12, 2000 at 09:46:26AM +1100, Eyal Lebedinsky wrote:
Alan Cox wrote:
2.2.18pre5
Just did a build on Debian2.2. Is it a misspellet
Date:Mon, 11 Sep 2000 13:08:59 +
From: Pravir Chandra [EMAIL PROTECTED]
I've been working to change the implementation of /dev/random over to the
Yarrow-160a algorithm created by Bruce Schneier and John Kelsey. We've been
working on parallel development for Linux and
Why? What's wrong with the current implementation. And more important
still: How well-known is Yarrow160A? I cannot find it in my copy of
[Schneier96], so it is probably not older than four years.
much of yarrow-160a has been specified by kelsey himself in discussions with
people at
Petr Vandrovec writes:
On 12 Sep 00 at 21:25, Keith Owens wrote:
0x85) vanish after the system has booted further. printk shows that
idt_table is correctly updated immediately after the set_system_gate
but once the system has booted the entries for my new traps have
reverted. (printk
On Mon, 11 Sep 2000, Jeff V. Merkey wrote:
Thanks Ted. I know, but a kernel debugger is one of those nasty pieaces
of software that can quickly get out of sync if it's maintained
separately from the tree -- the speed at which changes occur in Linux
would render it a very difficult project
Richard Guenther [EMAIL PROTECTED] wrote:
Whats the problem with just not allowing the module to unload at all?
Whats the point in unloading a module anyways. Ok, I know - debugging,
etc. - but for a "release" version this is not important. Also upgrading -
but for desktop boxes (for which
According to Alan Cox:
2.2.18pre5
2.2.18pre4
o Megaraid driver update (Peter Jarrett)
I just booted 2.2.18pre5, not having tried 2.2.18pre4 yet, on a
machine with an AMI Megaraid card.
During boot it hangs at:
megaraid: v1.11 (Aug 23, 2000)
megaraid: found
Hello!
On Tue, 12 Sep 2000, Bernd Jucknischke wrote:
With your patch test8 compiles but I get no sound. The chip is not
recognized during bootup (I have sound compiled in, not as a module). With
2.2.18pre2 it works well...
I have done the port of cs46xx.c from kernel 2.2 to 2.4 so I feel a
Date: Mon, 11 Sep 2000 17:51:20 -0600
From: "Jeff V. Merkey" [EMAIL PROTECTED]
I support source level in the kernel. Based on Andi Klein's review, I
have grabbed ext2utils and am looking at a minimal int 0x13 interface to
load files into memory. hardest problem here for Linux is
What does this mean?
recvmsg bug: copied 0 seq 476C726
it appeared in my dmesg output today.
--
Rob Murray
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
"Todd" == Todd [EMAIL PROTECTED] writes:
Jes Sorensen wrote: It took me a little while in the
beginning to convince Alteon to open up and provide docs, but
since they saw the light they have been extremely helpful and
went much further in their openness than I had ever expected or
[EMAIL PROTECTED] said:
Ah... I did misunderstand you. I thought you meant CONFIG_MODULES in
general, which'd be okay - obviously, if module support is disabled,
you can't load a module anyway.
Well actually, that's not strictly true. But it is fair to say that if
you're hacking new code
On Tue, 12 Sep 2000, Rik van Riel wrote:
The large IO delays I'm seeing in certain tests have
been traced back to the /elevator/ code. I think I'll
Actually the elevator works as in 2.2.15 (before any fix). The latency
settings are too high. They should be around 250 for reads and 500 for
On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote:
Normal users are only able to create a SIGIO signal when connecting.
That's very unlikely. TCP does not propagate gid/uid information over sockets,
not even over localhost.
However if something is looking at current- and the
On Tue, 12 Sep 2000, Alan Cox wrote:
That code example can in theory deadlock without any patches if the CPU's
Woops I really meant:
while (test_and_set_bit(0, lock));
/* critical section */
mb();
clear_bit(0, lock);
Andrea
-
To unsubscribe from this list:
"David" == David Ford [EMAIL PROTECTED] writes:
David C program instructions are in ASCII, data certainly isn't
David restricted to that. If you or your M*A can't or won't deal
David with anything but plain text, then filter it. Plain text is
David clearly in the minority of emails throughout
David Woodhouse [EMAIL PROTECTED] wrote:
You don't need to add another handler. I already overloaded the lcall7
handler by passing an extra int into it to tell it the type of call which is
causing it to be invoked. Values which are already used are 7 for iBCS calls
(lcall7) and 0x27 for
Andi Kleen wrote:
On Tue, Sep 12, 2000 at 11:33:31AM +0100, Alan Cox wrote:
Normal users are only able to create a SIGIO signal when connecting.
That's very unlikely. TCP does not propagate gid/uid information over sockets,
not even over localhost.
However if something is
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Tue, 12 Sep 2000, Rik van Riel wrote:
The large IO delays I'm seeing in certain tests have
been traced back to the /elevator/ code. I think I'll
Actually the elevator works as in 2.2.15 (before any fix). The
latency settings are too high.
On Tue, 12 Sep 2000, Rik van Riel wrote:
We simply keep track of how old the oldest request
in the queue is, and when that request is getting
too old (say 1/2 second), we /stop/ all the others
Going in function of time is obviously wrong. A blockdevice can write 1
request every two seconds or 1
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Tue, 12 Sep 2000, Rik van Riel wrote:
We simply keep track of how old the oldest request
in the queue is, and when that request is getting
too old (say 1/2 second), we /stop/ all the others
Going in function of time is obviously wrong. A
On Tue, 12 Sep 2000, Rik van Riel wrote:
Uhmmm, isn't the elevator about request /latency/ ?
Yes, but definitely not absolute "time" latency.
How do you get a 1msec latency for a read request out of a blockdevice
that writes 1 request in 2 seconds? See?
That was one of the first issues I was
Todd wrote:
While I agree with what's going on right now, the recent purchase of
Alteon by Nortel (primarily for their switch line, not for the
NICs) leaves quite a bit of doubt in my mind about the future of the card
and the openness of the firmware in particular.
Why not raise your
Oliver Neukum [EMAIL PROTECTED] wrote:
I think now that I'm probably best providing a generic pluggable syscall
handler, one that is very careful to make sure the syscall can't be entered
whilst the module is being unloaded.
This seems to me the best idea. However I would argue against
Dave Zarzycki wrote:
Personally speaking, I always thought it would be nice if the kernel
flushed dirty buffers right before a disk spins down. It seems silly to me
that a disk can spin down with writes pending.
Absolutely. That allows more time spun down too.
-- Jamie
-
To unsubscribe from
I'm not a big fan of Yarrow, since it (in my opinion) places too much
faith in the crypto algorithms. It uses a pathetically small entropy
pool, and assumes that hash function will do the rest. Which is fine,
but that makes it a pseudo-RNG, or a crypto-RNG, and not really an
entropy
[EMAIL PROTECTED] said:
But where do I get the other argument (struct pt_regs *) from? A
normal Linux syscall does not appear to have access to such a beast...
With difficulty. A normal syscall wouldn't generally go through the lcall7
handler. Some of the ABI/iBCS code gets access to the
Date:Mon, 11 Sep 2000 18:27:30 -0700
From: David Ford [EMAIL PROTECTED]
I've told Linus several times about this problems but he puts out one
test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
numerous
Going in function of time is obviously wrong. A blockdevice can write 1
request every two seconds or 1 request every msecond. You can't assume
anything in function of time _unless_ you have per harddisk timing
informations into the kernel.
Andrea - latency is time measured and perceived.
Jes Sorensen wrote:
So? I have one of those letters in my name as well, doesn't mean I put
it in the From line or in the code that I write. Or do you want us all
to start using a compiler and editors that will understand full UTF8
so everybody who use non roman character sets have their names
On Tue, 12 Sep 2000, Alan Cox wrote:
Andrea - latency is time measured and perceived. Doing it time based seems to
make reasonable sense. I grant you might want to play with the weighting per
When you have a device that writes a request every two seconds you still
want it not to seek all the
On Tue, 12 Sep 2000 14:54:29 +0100,
David Howells [EMAIL PROTECTED] wrote:
Oliver Neukum [EMAIL PROTECTED] wrote:
This seems to me the best idea. However I would argue against dynamically
allocating syscalls. Reserving numbers makes for better code and allows you
to do autoloading.
Now
Hello,
I need support for files larger than 2GB. What's the status for that ?
AFAIK neither 2.2 nor 2.4-test support that out of the box. Can anyone
point me to a good link for patches ? Apart from the kernel, does
anything else need changes for large file support ?
Thanks,
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Tue, 12 Sep 2000, Rik van Riel wrote:
Uhmmm, isn't the elevator about request /latency/ ?
Yes, but definitely not absolute "time" latency.
How do you get a 1msec latency for a read request out of a
blockdevice that writes 1 request in 2
I need support for files larger than 2GB. What's the status for that ?
2.2 + patches or 2.4 test and glibc 2.1.9x
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
I'm getting a lot of these:
(3c59x.c:LK1.1.8 13 Aug 2000 Donald Becker and others.
http://www.scyld.com/network/vortex.html $Revision: 1.102.2.25 $
See Documentation/networking/vortex.txt
eth0: 3Com PCI 3c905B Cyclone 100baseTx at 0xe000, 00:10:4b:6a:20:f3, IRQ 11
8K byte-wide RAM 5:3 Rx:Tx
On Tue, Sep 12, 2000 at 03:12:34PM +0100, Alan Cox wrote:
I need support for files larger than 2GB. What's the status for that ?
2.2 + patches or 2.4 test and glibc 2.1.9x
And make sure the utilities you want to work with those 2GB+ files were
compiled with -D_FILE_OFFSET_BITS=64 (check
Arnaud Installe writes:
Hello,
I need support for files larger than 2GB. What's the status for that ?
AFAIK neither 2.2 nor 2.4-test support that out of the box. Can anyone
point me to a good link for patches ? Apart from the kernel, does
anything else need changes for large file
Theodore Y. Ts'o wrote:
I've told Linus several times about this problems but he puts out one
test release after the other without this fixed.
This is kinda important, I run DNS tools which are threaded amongst
numerous other threaded programs a lot. What needs to be done to
On Tue, 12 Sep 2000, Rik van Riel wrote:
We can already set different figures for different drives.
Right.
Would it really be more than 30 minutes of work to put in
a different request # limit for each drive that automatically
satisfies the latency specified by the user?
Note that if you know
Andrea Arcangeli wrote:
Andrea - latency is time measured and perceived. Doing it time based
seems to make reasonable sense. I grant you might want to play with
the weighting per [device]
Right. Perception.
When you have a device that writes a request every two seconds you still
want it
I have a trivial question, is it possible to Open a Device Driver (A)
within and other Device Driver (B) and Handle the driver-A similar to how
an application uses the Driver.
It is certainly possible to call the same operations, yes, if done with
proper care. One example you could look at
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Tue, 12 Sep 2000, Rik van Riel wrote:
But you don't. Transfer rate is very much dependant on the
kind of load you're putting on the disk...
Transfer rate means `hdparm -t` in single user mode. Try it and
you'll see you'll get always the
First of all, thanks to all of you for your responses. :-) I was under
the impression 2.4 still didn't have large file support, as I seem to
recall ssize_t still was 32 bits.
On Tue, Sep 12, 2000 at 04:25:02PM +0200, Andreas Jaeger wrote:
Arnaud Installe writes:
Hello,
I need support
On Tue, Sep 12, 2000 at 03:00:29PM +0100, Paul Jakma wrote:
On Mon, 11 Sep 2000, Alan Cox wrote:
Shrug. So you want me to make it worse by shipping unproven code in a way
I can't test it ?
the code is in 2.4 and has been tested there though. the patches are a
backport of the 2.4
..so it should be at least as well tested as the USB backport in 2.2.18preX,
if not more so? Or so is implied. :)
This is the big clue most people are missing
2.2.17 - USB devices do not work
2.2.18 - USB=n no kernel change USB devices still do not work
On Tue, 12 Sep 2000, Rik van Riel wrote:
On Tue, 12 Sep 2000, Andrea Arcangeli wrote:
On Tue, 12 Sep 2000, Rik van Riel wrote:
Uhmmm, isn't the elevator about request /latency/ ?
Yes, but definitely not absolute "time" latency.
How do you get a 1msec latency for a read request
I really think Rik has it right here. In particular, an MP3 player needs to be able
to say, I have
X milliseconds of buffer so make my worst case latency X milliseconds. The number of
requests is
the wrong metric, because the time required per request depends on disk geometry, disk
caching,
On Tue, 12 Sep 2000, Hans Reiser wrote:
I really think Rik has it right here. In particular, an MP3 player
needs to be able to say, I have X milliseconds of buffer so make my
worst case latency X milliseconds. The number of requests is the
wrong metric, because the time required per
" " == Jeff Epler [EMAIL PROTECTED] writes:
I believe I have discovered a problem in the Linux 2.2 nfs
client. The short story is that NFS_CACHEINV(inode) does not
"act as a cache coherency point" (as nfs/file.c:nfs_lock()'s
comment implies) when multiple modifications
Date: Tue, 12 Sep 2000 09:56:12 +
From: Pravir Chandra [EMAIL PROTECTED]
i agree that the yarrow generator does place some faith on the crypto
cipher and the accumulator uses a hash, but current /dev/random
places faith on a crc and urandom uses a hash.
No, not true. The
In article [EMAIL PROTECTED] you write:
Dear list-readers,
I have a bad SDRAM chip with exactly one bit error. Memtest86 shows
that the bit error always occurs at the address 0x4eff508. I tried
to calculate the page number and it should be 20223.
...
Could someone tell me if there's another way
Chris Evans wrote:
On Tue, 12 Sep 2000, Hans Reiser wrote:
I really think Rik has it right here. In particular, an MP3 player
needs to be able to say, I have X milliseconds of buffer so make my
worst case latency X milliseconds. The number of requests is the
wrong metric, because
Hi David, Alan and Linus,
In June 1998, I spent 6 hours debugging and fixing a nasty data
corrupting bug. In October 1999, I finally had time to write a small
program to demonstrate that bug. Since then, I have spent 11 months
trying to get it fixed in the mainstream kernels. It is still
On Tue, 12 Sep 2000, Alan Cox wrote:
Now, I see people trying to introduce the concept of elapsed time into
that fix, which smells strongly of hack. How will this hack be cobbled
Actually my brain says that elapsed time based scheduling is the right
thing to do. It certainly works for
Cc; [EMAIL PROTECTED]
Today, I received duplicate messages as posted by Rik van Riel to this
list. Here are the headers from both messages. Other than identical
Message-ID's, I can't discern where the duplicate originated.
Good Luck.
First message
Received: (from
A prototype of Plug-in Schedulers for Linux as loadable modules
(for 3 Linux versions), white paper, and a sample implementation of
plug-in "processor sets" utilities and documents available at :
http://resourcemanagement.unixsolutions.hp.com/WaRM/schedpolicy.html
Try it out + tell us what you
For my project "dietlibc" (http://www.fefe.de/dietlibc/) I am looking
into implementing directory access now.
The kernel interface seems to be:
* supply an O_DIRECTORY flag to open()
* a getdents system call
You don't read on the fd in readdir, you call getdents.
getdents reads n struct
Hi Jeff,
since I vaguely remember an email from you describing how
you spent large amount of time tweaking and changing
the disk IO elevator in Netware, and since we might want
to improve the Linux elevator sort a bit, could you give
us some hints on what to do and where not to waste our
time?
Hello,
On a high load server, kernel has some errors:
VM: do_try_to_free_pages failed for httpd...
VM: do_try_to_free_pages failed for httpd...
eth0: Too much work at interrupt, status=0x4050.
eth0: Too much work at interrupt, status=0x4050.
is there somewhere the new version of driver for
On Tue, 12 Sep 2000, Rui Sousa wrote:
Rik van Riel wrote:
The second patch is a new version of the VM patch, [snip]
http://www.surriel.com/patches/
Gave your patch a try, only the vm one. I applied it against
2.4.0-test8 (final) with some warnings so the bug report may not
be
If you're logging in as root, this is probably a result of the VT not
being named in /etc/securetty. Devfsd mucks up the names, so you can
either include "1," which would allow root logins from pseudo-terminals
and other insecure places, or upgrade your util-linux to a newer
version; I'm not
If we have a purely Linux-specific hack to ensure cache coherency,
that will still corrupt the cache on those *NIX clients that use
ordinary cache coherency checking (i.e. checking mtime + file size)
rather than cache invalidation.
Its what Solaris implements and what SunOS back down to 3.x
1 - 100 of 393 matches
Mail list logo
