A new version 0.9.2 is available with some bug fixes
and a explanation of the code.
download:
patch for kernel 2.2.17 and administration tool.
http://www.bronzesoft.org/projects/scfw/ip_scfw-0.9.2.tar.gz
Read the description of the idea:
http://www.bronzesoft.org/projects/scfw/doc.html
Richard B. Johnson writes:
> On Sun, 22 Oct 2000, Dwayne C . Litzenberger wrote:
> o Once installed, a kernel module is every bit as "efficient"
> as some driver linked into the kernel at build-time. Of course
I doubt this is true on most modern processors. On the Pentium
and above, large
hi kernelList,
i readed this thread and had the hope that it will fix my problem.
i have an older quad 166Mhz ppro machine with an intel mainbord.
it runs only with kernel command NOAPIC.
tried kernels from 2.2.15 to 2.4.0-test9.
with apic, it will boot till init of the first adaptecController
> " " == Matti Aarnio <[EMAIL PROTECTED]> writes:
> The NFSv3 CLIENT code must do post-open verification, that if
> the opened file has size exceeding 2G-1, and O_LARGEFILE flag
> is not set, the opened file must be closed, and caller must be
Just out of curiosity: why can
> " " == Andrea Arcangeli <[EMAIL PROTECTED]> writes:
> On Wed, Oct 25, 2000 at 09:34:49PM +0200, Trond Myklebust
> wrote:
>> All NFSv3 operations are 64-bit and LFS-compliant. There's
>> therefore no need for an O_LARGEFILE flag.
> I don't understand what you mean,
On Wed, Oct 25, 2000 at 12:53:38PM -0700, Vitaly Luban wrote:
> Hi,
>
> I've got a PCI resource conflict on PowerPC Motorola MCP 750 system
> while booting 2.4.0-test10. It works happily under 2.2.16 w/o any problems.
> messages and lspci for 2.2.16 and 2.4.0-test10 attached.
[snip]
>
On Thu, 26 Oct 2000, Stephen Rothwell wrote:
> However, on the bus this morning, I though about this again and wondered
> that this may not the correct way to do this. What we actually want to
> power manage is the PCI device as a whole not each interface independantly,
> which I would assume
It's for a good cause.
Andre Hedrick
The Linux ATA/IDE guy
-- Forwarded message --
Date: 25 Oct 2000 17:59:47 -0400
From: LinuxWorld <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: Autographed Linus Torvalds Photo Auction!
This message is brought to you by LinuxWorld
On Thu, Oct 26, 2000 at 03:56:46AM +0200, Andi Kleen wrote:
> a 4GB-1 file.
Side note: 4GB-2 since -1 means "ignore".
Andrea
-
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/
On Thu, Oct 26, 2000 at 02:17:31AM +0200, Andrea Arcangeli wrote:
> > INTEL as well as the feature bit before enabling XMM and FXSR features (AMD
> > also has fxsr, but we currently don't do anything with it). I moved the
>
> FXSR is supported and it just works fine on Athlon too with the PIII
On Thu, Oct 26, 2000 at 12:06:17AM +0200, Andrea Arcangeli wrote:
> 2.2.18pre17aa1 allows anybody to open a file larger than 2G (that seems not to
> be completly in sync with the specs) but it has all the necessary runtime
> checks during read/write. Just search for O_LARGEFILE in the lfs patch.
Andreas Dilger wrote:
>
> You write:
> There is a tool to recover the whole partition table, gpart, if
> your partition table is corrupt. However, it sounds more like
> just the filesystem is corrupt.
Partition table seems well. I can mount other filesystems from that
disk.
> Since you have a
In article <[EMAIL PROTECTED]> you wrote:
> make oldconfig clean dep all install modules modules_install
> Makefiles are puzzling, sometimes.
make dep does something that's basically equivalent to changing
the Makefiles. However, make doesn't re-read them, so all the
targets after "dep" will be
Followup to: <[EMAIL PROTECTED]>
By author:Doug Ledford <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> On that specific bit I haven't seen it go out of sync yet. However, I program
> it defensively because I already got bit by the fact that the X86_FEATURE_PN
> bit on Intel means
Andrea Arcangeli wrote:
>
> On Wed, Oct 25, 2000 at 02:46:19PM -0400, Doug Ledford wrote:
> > @@ -214,8 +215,8 @@
> > movb ready,%al # First CPU if 0
> > orb %al,%al
> > jz 4f # First CPU skip this stuff
> > - movl %cr4,%eax # Turn on 4Mb
On Wed, Oct 25, 2000 at 02:46:19PM -0400, Doug Ledford wrote:
> @@ -214,8 +215,8 @@
> movb ready,%al # First CPU if 0
> orb %al,%al
> jz 4f # First CPU skip this stuff
> - movl %cr4,%eax # Turn on 4Mb pages
> - orl $16,%eax
> +
Due to an unexpected problem, the kernel.org downtime will be extended
until some time tomorrow. In the meantime, please use a mirror :)
-hpa
--
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
You write:
> Could somebody can tell me where I can read about recovering
> (rather very) damaged e2fs partition ?
There is a tool to recover the whole partition table, gpart, if
your partition table is corrupt. However, it sounds more like
just the filesystem is corrupt.
> First, I've made a
Andrea Arcangeli wrote:
>
> On Wed, Oct 25, 2000 at 02:46:19PM -0400, Doug Ledford wrote:
> > I've made a few correctness changes to this code. Items that needed to be
> > corrected for include the facts that the XMM feature bit is an Intel specific
> > bit that other vendors may use for other
On Wed, Oct 25, 2000 at 02:46:19PM -0400, Doug Ledford wrote:
> I've made a few correctness changes to this code. Items that needed to be
> corrected for include the facts that the XMM feature bit is an Intel specific
> bit that other vendors may use for other things, so you need to test vendor
Petr Vandrovec writes:
> Sure it does not. Selectors point to linear addresses, before passing them
> through pagetables. You have 32+14 bits of virtual address (32 = offset,
> 14 = valid bits in selector), which are translated, together with
> offset, to 32 bit linear address. This 32bit linear
Not.
It does not lock anything else...
This was not a problem.
/RogerL
Roger Larsson wrote:
>
> Hi again,
>
> Please ignore my patch suggestion from getblk -
> it will give problems later - in alloc...
>
> It is grow_buffers that might need to lock the
> other ones too...
>
> /RogerL
>
>
Hi,
Something happened, I don't know really what.
I was backing up 250MB directory from hdc2 (fat32),
mounted as /hdc2 to /hdb1 (fat32) using commands:
cd /hdc2
tar cvf /hdb1/copy.tar .
(I don't see anything wrong in that.)
After archive creation I have found destroyed hda3
(sorry, I don't
* David Schwartz <[EMAIL PROTECTED]> [001025 15:35] wrote:
>
> If a programmer does not ever wish to block under any circumstances, it's
> his obligation to communicate this desire to the implementation. Otherwise,
> the implementation can block if it doesn't have data or an error available
> at
Alexander Viro wrote:
>
> On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
>
> > > > :%s/have/doesn't have/gc
> > >
> > > ??? Why the hell do you want a global replacement?
> >
> > not global replace, global CONFIRM. Just in case the
>
> Ugh. If you want to be pedantic that's G1:/have/s//doesn't
On Wed, Oct 25, 2000 at 11:27:09AM -0400, Simon Kirby wrote:
> On Wed, Oct 25, 2000 at 01:02:46AM -0500, Jonathan Lemon wrote:
>
> > ends up making the job of the application harder. A simple example
> > to illustrate the point: what if the application does not choose
> > to read all the data
Hi
I've got a 486 running 2.4.0-test9 which I am using as a router
between my network and cable modem. I've noticed that ping times (even
on loopback) are significantly higher than on 2.2.16. This box is
doing masquerading for stuff going out the cable interface which is a
realtek 8039. The
> On Wed, Oct 25, 2000 at 03:11:37PM -0700, David Schwartz wrote:
> >
> > > Now, next time around the loop, we get a notification for an event
> > > when there is no data to read. The application now must be prepared
> > > to handle this case (meaning no blocking read() calls can be used).
> >
Hi together,
Paul Bristow wrote:
>
> I'll get on it. I just tidied up the previous patch for Clik! support
> and fixed the last bug so that *should* wrap up 2.2.x.
Wonderful, so I can hope for a good solution soon :-)
BTW (for Jens): I noticed some other removable device problems
with
On Wed, Oct 25, 2000 at 03:11:37PM -0700, David Schwartz wrote:
>
> > Now, next time around the loop, we get a notification for an event
> > when there is no data to read. The application now must be prepared
> > to handle this case (meaning no blocking read() calls can be used).
> > --
> >
Hi Andre,
Andre Hedrick <[EMAIL PROTECTED]> writes:
>
> You want to get ATA/PI APM fixed?
Absolutely :-)
> "The Linux 'original' IDE guy' Mark Lord showed Alan what was trying to
> bang over everyone's head, without success.
>
> Here is his sample code for cs5530 chipset.
>
> Look at this
Hi again,
Please ignore my patch suggestion from getblk -
it will give problems later - in alloc...
It is grow_buffers that might need to lock the
other ones too...
/RogerL
--
Home page:
http://www.norran.net/nra02596/
-
To unsubscribe from this list: send the line "unsubscribe
> Now, next time around the loop, we get a notification for an event
> when there is no data to read. The application now must be prepared
> to handle this case (meaning no blocking read() calls can be used).
> --
> Jonathan
If the programmer never wants to block in a read call, he
Found a strange one.
getblk releases hash_table_lock and lru_list_lock
before calling refill_freelist that calls grow_buffers
that locks free_list[].lock
- lru_lock and hash_table_lock not held, violating
deadlock prevention rules in beginning of file.
patch.
in getblk move the call to
On Wed, Oct 25 2000, Nick Piggin wrote:
> Did the following with 2.4.0-test9 + reiserfs 3.6.18 (all ext2 filesystem,
> however) and all ide block devices.
>
> scsi0 : SCSI host adapter emulation for IDE ATAPI devices
> Vendor: RICOH Model: CD-R/RW MP7060A Rev: 1.50
> Type: CD-ROM
On Wed, Oct 25, 2000 at 10:49:52PM +0200, Trond Myklebust wrote:
> This should already be done IIRC. At least nfsd_open() always sets
> O_LARGEFILE.
Yes, that is just working right.
> we should be returning EOVERFLOW rather than EBIG.
Right.
2.4.0-test10-pre4 is also buggy because it doesn't
It may work, but the bridge secondary/subordinate numbers look wrong.
I am pondering if the bus numbering/bridging stuff shouldn't be given a
good looking-over. I have the wonderful _PCI System Architecture, 4th
Ed._ in my hands, and it describes PCI-PCI bridge init in great detail,
including
msgsnd seems to be corrupting memory around the msgbuf pointer.
for example I have the following code:
pMsgBuf = malloc(iPacketLen + 4 + 8);
bzero(pMsgBuf, iPacketLen + 4 + 8);
pMsgBuf += 4; /* Build a guard band */
printf("PMQ:pMsgBuf: %p\n",pMsgBuf);
printf("PMQ:-4: %p\n", *(pMsgBuf-4));
rc
On Wed, Oct 25, 2000 at 11:40:28AM -0700, Simon Kirby wrote:
> On Wed, Oct 25, 2000 at 12:23:07PM -0500, Jonathan Lemon wrote:
>
> > Consider a program which reads from point A, writes to point B. If
> > the buffer associated with B fills up, then we don't want to continue
> > reading from A.
>
On Wed, Oct 25, 2000 at 11:25:14PM +0300, Matti Aarnio wrote:
> The NFSv3 SERVER (for which Andrea made his patch)
> actually MUST open local files with O_LARGEFILE
> flag set. (Otherwise e.g. EXT2 may reject the open.)
Exactly, that is the code-sharing implementation detail I
Hi,
I noted that even try_to_free_buffers locks lru_list_lock.
Then it tries to lock some others - maybe one of the other treads
got one of those (hash_table_lock, free_list[index].lock)
It fits with that proc 4 it executes in the beginning of
try_to_free_buffers, does it move?
Or is it stuck at
On Wed, Oct 25, 2000 at 09:34:49PM +0200, Trond Myklebust wrote:
> All NFSv3 operations are 64-bit and LFS-compliant. There's therefore
> no need for an O_LARGEFILE flag.
I don't understand what you mean, sorry.
Userspace programs must open with O_LARGEFILE to go over 2G. This is true
Hello,
I hope I'm sending this email to the right people, otherwise excuse me
please and forward it.
Here is my problem:
My computer is a Compaq proliant ML350 with a smart controler ultra2
wide scsi.
I installed the redhat 6.2 with a kernel 2.2.13 (but the problem occurs
even with 2.2.17),
the
On Wed, Oct 25, 2000 at 09:40:53PM +0200, Jamie Lokier wrote:
> Simon Kirby wrote:
> > And you'd need to take the descriptor out of the read() set in the
> > select() case anyway, so I don't really see what's different.
>
> The difference is that taking a bit out of select()'s bitmap is
>
On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> > > :%s/have/doesn't have/gc
> >
> > ??? Why the hell do you want a global replacement?
>
> not global replace, global CONFIRM. Just in case the
Ugh. If you want to be pedantic that's G1:/have/s//doesn't &^M
for you.
-
To unsubscribe from this
> I am getting these messages during boot. It happens
> from test9 until test10-pre5.
Including test10-pre5 ?
I don't have this problem, but I'm using
modutils 2.3.15. I'll upgrade to
and try that.
After you load this kernel, can you:
cd linux/drivers/usb
insmod printer.o; insmod
On Tue, 24 Oct 2000, Brian Gerst wrote:
> [EMAIL PROTECTED] wrote:
> >
> > I just switched from 2.2.17pre9 to 2.4.0pre9, and my joystick won't work
> > anymore. It's an analog joystick connected to an AudioPCI sound card. I
> > can get it initialized, but I can not access it, it seems it does
Alexander Viro wrote:
>
> > > > > (e.g. generic_commit_write have to mess with i_size value to update the
> > > ^^^
> > > Ugh. s/have/doesn't have/, indeed. Sorry.
> >
> > Wrong syntax:
> >
> > :%s/have/doesn't have/gc
>
> ??? Why the hell do you want a
> On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
>
> > Alexander Viro wrote:
> > >
> > > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> > >
> > > > Al,
> > > >
> > > > Thanks. I'll print this one out and post it on the wall for tonight's
> > > > debugging session.
> > > [snip]
> > > > > (e.g.
On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> Alexander Viro wrote:
> >
> > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> >
> > > Al,
> > >
> > > Thanks. I'll print this one out and post it on the wall for tonight's
> > > debugging session.
> > [snip]
> > > > (e.g. generic_commit_write have
> Matti Aarnio <[EMAIL PROTECTED]> writes:
> The NFSv3 SERVER (for which Andrea made his patch) actually
> MUST open local files with O_LARGEFILE flag set. (Otherwise
> e.g. EXT2 may reject the open.)
This should already be done IIRC. At least nfsd_open() always sets
> What applications would do better by postponing some of the reading?
> I can't think of any reason off the top of my head why an application
> wouldn't want to read everything it can. Doing everything in smaller
> chunks would increase overhead (but maybe reduce latencies very slightly
> --
Erik Andersen wrote:
>
> On Wed Oct 25, 2000 at 02:15:05PM -0600, Jeff V. Merkey wrote:
> >
> >
> > Alexander Viro wrote:
> > >
> > > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> > >
> > > > Al,
> > > >
> > > > Thanks. I'll print this one out and post it on the wall for tonight's
> > > >
On Wed Oct 25, 2000 at 02:15:05PM -0600, Jeff V. Merkey wrote:
>
>
> Alexander Viro wrote:
> >
> > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> >
> > > Al,
> > >
> > > Thanks. I'll print this one out and post it on the wall for tonight's
> > > debugging session.
> > [snip]
> > > > (e.g.
Tigran Aivazian wrote:
>
> Hi guys,
>
> When running SPEC SFS tests against 2.4.0-test10-pre4 on a 4-way SMP
> machine with 6G RAM (highmem+PAE enabled) I got
>
> __alloc_pages: 0-order allocation failed.
>
> (probably coming from nfsd, why don't we print eip of the caller there?)
>
> and
On Wed, Oct 25, 2000 at 09:34:49PM +0200, Trond Myklebust wrote:
> > " " == Matti Aarnio <[EMAIL PROTECTED]> writes:
> >When the NFS server does file open, does it do it with
> >O_LARGEFILE, or not ? Is there a standardized way to pass
> >that flag over NFSv3 ?
>
On Tue, Oct 24, 2000 at 06:47:30PM -0700, Hunt Kent wrote:
> Hi,
>
> I am getting these messages during boot. It happens from test9 until
> test10-pre5. The last kernel that worked fine was test9-pre7. I have
> not tested test9-pre[8-9].
>
> modutils 2.3.16
>
> Calculating module
Andrew Morton wrote:
> But all the documentation has for years been saying that
> 2.7.2.3 is the one true compiler, so we are now in for 12
> months worth of bogus oops reports.
>
> This patch will help:
>
> --- linux-2.4.0-test10-pre5/arch/i386/kernel/setup.cTue Oct 24
[...]
> +
> +#if
On Wed, Oct 25 2000, Andre Hedrick wrote:
> > The optimal solution is to make the UDF tools part of the util-linux
> > package, which will probably happen at some point. I don't really know,
> > that part is not mine. I might put some work into making this happen,
> > though.
>
> Andries,
>
>
Alexander Viro wrote:
>
> On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
>
> > Al,
> >
> > Thanks. I'll print this one out and post it on the wall for tonight's
> > debugging session.
> [snip]
> > > (e.g. generic_commit_write have to mess with i_size value to update the
>
Hi guys,
When running SPEC SFS tests against 2.4.0-test10-pre4 on a 4-way SMP
machine with 6G RAM (highmem+PAE enabled) I got
__alloc_pages: 0-order allocation failed.
(probably coming from nfsd, why don't we print eip of the caller there?)
and the machine locked up (but pingable). So I
Hi,
I've got a PCI resource conflict on PowerPC Motorola MCP 750 system
while booting 2.4.0-test10. It works happily under 2.2.16 w/o any problems.
messages and lspci for 2.2.16 and 2.4.0-test10 attached.
I'd be grateful on any comments, thanks :)
BTW, Martin, do you know why to complain about
I am attempting to build everything as modules.
I can compile the works, but depmod -ae gives
loads of errors. Are these bugs or user error?
Thanks,
Miles
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-test10/kernel/drivers/block/DAC960.o
depmod: devfs_unregister_blkdev
On Wed Oct 25, 2000 at 12:16:40PM -0700, H. Peter Anvin wrote:
> Erik Andersen wrote:
> >
> > On Wed Oct 25, 2000 at 11:43:02AM -0700, H. Peter Anvin wrote:
> > >
> > > There is another good reason to ditch /etc/mtab: as a static file, it
> >
> > And it is supposed to be writable though it
On Wed, Oct 25 2000, Tom Holroyd wrote:
> Alpha DP264 UP.
>
> Doing a dump to a SCSI MO disk (aic7xxx, Fujitsu Gigamo, ro ext2 fs), and
> simultaneously writing a megabyte to a floppy (tar -cf /dev/fd0, "FDC 0 is
> a post-1991 82077") produced a ten second freeze. I did this twice and
> it's
Simon Kirby wrote:
> And you'd need to take the descriptor out of the read() set in the
> select() case anyway, so I don't really see what's different.
The difference is that taking a bit out of select()'s bitmap is
basically free. Whereas the equivalent with events is a bind_event()
system
This text is about how edge-triggered events can work, but they must be
the right kind of edges if they are to be efficient. With suggestions.
Simon Kirby wrote:
> What happens at "wait until output is ready for writing then goto 6"?
> You mean you would stop the main loop to wait for a single
> " " == Matti Aarnio <[EMAIL PROTECTED]> writes:
>When the NFS server does file open, does it do it with
>O_LARGEFILE, or not ? Is there a standardized way to pass
>that flag over NFSv3 ?
All NFSv3 operations are 64-bit and LFS-compliant. There's therefore
no
"H. Peter Anvin" wrote:
>
> Erik Andersen wrote:
> >
> > On Wed Oct 25, 2000 at 11:43:02AM -0700, H. Peter Anvin wrote:
> > >
> > > There is another good reason to ditch /etc/mtab: as a static file, it
> >
> > And it is supposed to be writable though it lives in /etc. It should live
> > in
Followup to: <[EMAIL PROTECTED]>
By author:Doug Ledford <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I've made a few correctness changes to this code. Items that needed to be
> corrected for include the facts that the XMM feature bit is an Intel specific
> bit that other vendors
On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> Al,
>
> Thanks. I'll print this one out and post it on the wall for tonight's
> debugging session.
[snip]
> > (e.g. generic_commit_write have to mess with i_size value to update the
^^^
Ugh. s/have/doesn't have/,
On Wed Oct 25, 2000 at 11:43:02AM -0700, H. Peter Anvin wrote:
>
> There is another good reason to ditch /etc/mtab: as a static file, it
And it is supposed to be writable though it lives in /etc. It should live
in /var. Has the LSB ever gotten around to addressing this wart?
This is a pita
On Wed, 25 Oct 2000, Jens Axboe wrote:
> On Tue, Oct 24 2000, Jeff V. Merkey wrote:
> > > Are you suggesting the tools be part of the kernel tree? If you are, I
> > > don't think they belong here because they are userland tools like
> > > mkisofs and the like. Nothing really related to the
After looking at the various other patches that people posted, I've come
up with this revised version of my original...
-Barry K. Nathan <[EMAIL PROTECTED]>
diff -ruN linux-2.4.0test10pre5/Documentation/Changes
linux-2.4.0test10pre5-bkn/Documentation/Changes
---
On Wed Oct 25, 2000 at 08:16:07PM +0200, Andries Brouwer wrote:
>
> Your web page misses the loop device info.
>
> Another point of difference is the name of the root device.
> /proc/mounts has /dev/root, while /etc/mtab usually has
> whatever was listed for / in /etc/fstab.
>
> For some
Jens Axboe wrote:
>
> On Tue, Oct 24 2000, Jeff V. Merkey wrote:
> > > Are you suggesting the tools be part of the kernel tree? If you are, I
> > > don't think they belong here because they are userland tools like
> > > mkisofs and the like. Nothing really related to the kernel.
> >
> > No.
On Wed, 25 Oct 2000, Albert D. Cahalan wrote:
> > o Pentium IV support.
> >- Now recognised as i686 instead of i1586.
> This seems wrong.
It is/was.
This has since been fixed in recent pre-patches for
over a week now.
Dave.
--
| Dave Jones <[EMAIL PROTECTED]> http://www.suse.de/~davej
Rik van Riel wrote:
>
> On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> > Rik van Riel wrote:
> > > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> > >
> > > > I've reviewed the patch. It's affect seems minimal and will not
> > > > break NWFS as proposed -- it looks like, however, it will reduce
>
On Tue, Oct 24 2000, Jeff V. Merkey wrote:
> > Are you suggesting the tools be part of the kernel tree? If you are, I
> > don't think they belong here because they are userland tools like
> > mkisofs and the like. Nothing really related to the kernel.
>
> No. I'm suggesting they be in the utils
Al,
Thanks. I'll print this one out and post it on the wall for tonight's
debugging session.
:-)
Jeff
Alexander Viro wrote:
>
> On Wed, 25 Oct 2000, Alexander Viro wrote:
>
> > I can do the proof-of-concept patch (below 10Kb, ext2 + generic code, with
> > the need to repeat the
On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> Rik van Riel wrote:
> > On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> >
> > > I've reviewed the patch. It's affect seems minimal and will not
> > > break NWFS as proposed -- it looks like, however, it will reduce
> > > the performance slightly of
Andrea Arcangeli wrote:
> 2.2.18pre15aa1 is here (I will include in the next aa patchkit):
>
>
>ftp://ftp.us.kernel.org/pub/linux/kernel/people/andrea/patches/v2.2/2.2.18pre15aa1/PIII-3.bz2
>
> Such patch is been generated by a mix of PIII 2.2.x patch and the PIII 2.4.x
> support plus
Octave,
Andrea fixed a corruption problem which looks exactly what you're
hitting.
Please try
ftp://ftp.kernel.org/pub/people/andrea/patches/v2.2/2.2.18pre17/VM-global-2.2.18pre17-7.bz2
On Wed, 25 Oct 2000, octave klaba wrote:
> Hi,
> We test a smp server (bi-piii) and we have
> some
Rik van Riel wrote:
>
> On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
>
> > I've reviewed the patch. It's affect seems minimal and will not
> > break NWFS as proposed -- it looks like, however, it will reduce
> > the performance slightly of EXT2/3 with iozone for read ahead
> > since the first
On Wed, 25 Oct 2000, Alexander Viro wrote:
> I can do the proof-of-concept patch (below 10Kb, ext2 + generic code, with
> the need to repeat the fs-specific parts for other filesystems) in an
> hour. Clearance?
OK, it didn't take an hour. Warning: completely untested, needs
(trivial) changes
Followup to: <[EMAIL PROTECTED]>
By author:Andries Brouwer <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> First of all, let me quote mount(8):
>
> -
>The programs mount and umount maintain a list of
On Wed, Oct 25, 2000 at 12:23:07PM -0500, Jonathan Lemon wrote:
> Consider a program which reads from point A, writes to point B. If
> the buffer associated with B fills up, then we don't want to continue
> reading from A.
>
> A/B may be network sockets, pipes, or ptys.
Fine, but we
On Wed, 25 Oct 2000, Jeff V. Merkey wrote:
> I've reviewed the patch. It's affect seems minimal and will not
> break NWFS as proposed -- it looks like, however, it will reduce
> the performance slightly of EXT2/3 with iozone for read ahead
> since the first section of the patch limits the read
On Wed, Oct 25, 2000 at 07:08:48PM +0200, Jamie Lokier wrote:
> Simon Kirby wrote:
>
> > What applications would do better by postponing some of the reading?
> > I can't think of any reason off the top of my head why an application
> > wouldn't want to read everything it can.
>
> Pipelined
Rik,
I've reviewed the patch. It's affect seems minimal and will not break
NWFS as proposed -- it looks like, however, it will reduce the
performance slightly of EXT2/3 with iozone for read ahead since the
first section of the patch limits the read ahead window size. NWFS uses
it's own read
In serial.c, it appears that unless do_autoconfig() is called through an
ioctl() call, the variable state->type, which is used to index into the
uart_config[] array, is not set, resulting in problems (I'm working with
a mips embedded board). Why not set info->type from sstate->type in
On Wed, Oct 25, 2000 at 10:59:13AM +0200, Christian Czezatke wrote:
> I've recently run across some problems with /proc/mounts on Linux 2.2.17
> when trying to get rid of /etc/mtab in favor of /proc/mounts.
>
> Patches that are basically a backport of the 2.4.x implementation of
>
Where's the patch located? It's not attached to this email.
Jeff
Rik van Riel wrote:
>
> On Wed, 25 Oct 2000, Alexander Viro wrote:
> > On Wed, 25 Oct 2000, Rik van Riel wrote:
> >
> > > Anyway, below is a patch that implements Al Viro's
> > > readahead fix and one small readahead adjustment
> o Pentium IV support.
>- Now recognised as i686 instead of i1586.
This seems wrong.
Remember that we are simply following the old pre-Pentium
naming tradition. Since the "Pentium 4" does not use the
old "P6" core (like the Pentium Pro, Pentium II, Pentium III,
and Celeron did) it is the
On Wed, Oct 25, 2000 at 01:42:52PM +0200, Martin Mares wrote:
> Hello!
>
> > "The Linux 'original' IDE guy' Mark Lord showed Alan what was trying to
> > bang over everyone's head, without success.
> >
> > Here is his sample code for cs5530 chipset.
> >
> > Look at this and comment. I have
Alexander Viro wrote:
>
> On Wed, 25 Oct 2000, Linus Torvalds wrote:
>
> >
> >
> > On Wed, 25 Oct 2000, Rik van Riel wrote:
> > >
> > > OTOH, block-dev readahead makes sense for filesystems where
> > > the packing locality is close to the access pattern BUT NOT
> > > close to anything the
On Wed, 25 Oct 2000, Alexander Viro wrote:
> On Wed, 25 Oct 2000, Rik van Riel wrote:
>
> > Anyway, below is a patch that implements Al Viro's
> > readahead fix and one small readahead adjustment
> > that seems to make sense ...
>
> Rik, doesn't said fix need propagation into your adjustment?
On Wed, 25 Oct 2000, Rik van Riel wrote:
> Anyway, below is a patch that implements Al Viro's
> readahead fix and one small readahead adjustment
> that seems to make sense ...
Rik, doesn't said fix need propagation into your adjustment?
-
To unsubscribe from this list: send the line
On Wed, 25 Oct 2000, Linus Torvalds wrote:
>
>
> On Wed, 25 Oct 2000, Rik van Riel wrote:
> >
> > OTOH, block-dev readahead makes sense for filesystems where
> > the packing locality is close to the access pattern BUT NOT
> > close to anything the page cache would recognise as being
> >
Hi,
We test a smp server (bi-piii) and we have
some problems when the bandwidth is more than 16Mbs:
it crashs.
Is there any way to fix it ?
thanks for help
octave
eth0: card reports no resources
VFS: file-max limit 4096 reached
Kernel panic: VFS: LRU block list corrupted.
Kernel panic: VFS:
1 - 100 of 328 matches
Mail list logo
