On Sat, 9 Jun 2001, Dawson Engler wrote:
> >
> > Good point. Spinlocks (with the exception of read-read locks, of course)
> > and semaphores will deadlock on recursive use, while the BKL has this
> > "process usage counter" recursion protection.
>
> Actually, it did show up all over the place
Andrew,
Although I don't run
Redhat, your response
tells me that, even though I
was feeling that it was a
kernel problem, it could be
a userspace issue, which I
also suspected. Debian
updated their nettools
today, so I will see if that
helps in any way. Thanks
for your
Andrew,
Although I don't run Redhat, your response tells me that, even though I was feeling that it was a kernel problem, it could be a userspace issue, which I also suspected. Debian updated their nettools today, so I will see if that helps in any way. Thanks for your help.
Glenn C.
On Sat, 9 Jun 2001, watermodem wrote:
> Mike Galbraith wrote:
> >
> > On Thu, 7 Jun 2001, watermodem wrote:
> >
> > > "David S. Miller" wrote:
> > > >
> > > > George Bonser writes:
> > > > > There is, of course, one basic problem with that argument. While you can say
> > > > > (and probably
[Request For Testers ... patch below]
Hi,
during my holidays I've written the following patch (forward-ported
to 2.4.6-pre2 and improved a tad today), which implements these
improvements to page_launder():
1) don't "roll over" inactive_dirty pages to the back of the
list, but reclaim them
watermodem <[EMAIL PROTECTED]> said:
[...]
> He is discussing a theme with legal implications. (Legal and Slow tended
> to be intertwined) I know what his position in the linux kernel
> hierarchy is, and if he were in a corporation with that position he
> could just say NO without any reason.
> On Sat, 9 Jun 2001, Alexander Viro wrote:
> >
> > Another difference from spinlocks is that BKL is recursive. I'm
> > actually surprised that it didn't show up first.
>
> Good point. Spinlocks (with the exception of read-read locks, of course)
> and semaphores will deadlock on recursive use,
"Bulent Abali" <[EMAIL PROTECTED]> writes:
> >Bulent,
> >
> >Could you please check if 2.4.6-pre2+the schedule patch has better
> >swapoff behaviour for you?
>
> Marcelo,
>
> It works as expected. Doesn't lockup the box however swapoff keeps burning
> the CPU cycles. It took 4 1/2 minutes to
> Indeed; the bug in the uuid_strategy which you pointed out in the
> random driver wasn't caused by the fact that we were using a
> user-specified length (since the length was being capped to a maximum
> value of 16). The security bug was that the test was done on a signed
> value, and
> Struct padding is a problem. Really, there shouldn't be any
> implicit padding. This causes:
>
> 1. security leaks when such structs are copied to userspace
>(the implicit padding is uninitialized, and so may contain
>a chunk of somebody's private key or password)
>
> 2. bloat, when
Daniel Phillips wrote:
>
> This is easy, just set the list head to the page about to be truncated.
Works for me.
--- linux-2.4.5/mm/filemap.cMon May 28 13:31:49 2001
+++ linux-akpm/mm/filemap.c Sun Jun 10 11:29:19 2001
@@ -235,12 +235,13 @@
/* Is one of the pages to
"Glenn C. Hofmann" wrote:
>
> I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results. Everything boots
> great and I can login fine. When I try to assign an IP via DHCP or ifconfig, the
>system
> sits and stares at me indefinitely. 2.4.5-pre4 didn't compile for me, but pre3
>works
This patch fixes compile warnings when using gcc 3.0 cvs snapshots. It
makes the following changes:
- Removes warnings about trigraphs (done by patching the Makefile in top
directory
- changes text at the end of #endif statements to comments
- fixes warnings about use of labels at the end
Hi,
I am trying to integrate binfmt_xout.c into kernel 2.4 as part of the
linux-abi project (formerly known as iBCS). For old Xenix 286 binaries the
lcall7 gate needs to part of the LDT.
In kernels 2.0 sys_modify_ldt(0,...) used to return the default_ldt (with
lcall7 gate) if there were no
> Is it me or does this patch forget to change the kernel version? ;-)
> make menuconfig reports pre1 still.. oh well no biggie..
yes, this is a mistake. the Makefile had not been updated.
--
Adam
http://www.eax.com The Supreme Headquarters of the 32 bit registers
-
To unsubscribe from
Is it me or does this patch forget to change the kernel version? ;-)
make menuconfig reports pre1 still.. oh well no biggie..
Shawn.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
New: man-pages 1.38, with for the first time over 1000 pages.
Undocumented system calls include:
rt_sigreturn, rt_sigaction, rt_sigprocmask, rt_sigpending,
rt_sigtimedwait, rt_sigqueueinfo, rt_sigsuspend,
sigaltstack, getpmsg, putpmsg, ugetrlimit, mmap2,
madvise.
Contributions are
[EMAIL PROTECTED] said:
> Riley Williams writes:
> > Even if that wasn't true, aren't the above all self-recursive
> > definitions that would prevent anything calling them from compiling?
> Yes, it looks that way.
cpp doesn't recurse.
--
dwmw2
-
To unsubscribe from this list: send the
> BTW, what is the officially approved way to open a device on a
> dynamic misc minor? Reading /proc/misc for the minor number,
Ask for minor 0 I believe, then load the module then see what you got.
> then mknod'ing a device and opening it seems to me to have a
> nasty race condition, am I
On Sat, 9 Jun 2001, watermodem wrote:
> He is discussing a theme with legal implications. (Legal and Slow tended
> to be intertwined) I know what his position in the linux kernel
> hierarchy is, and if he were in a corporation with that position he
> could just say NO without any reason.
On Saturday 09 June 2001 19:40, Alexander Viro wrote:
> > takes 45 seconds CPU time due to the O(clean * dirty) algorithm in
> > truncate_inode_pages(). The machine is locked up for the duration.
> > The patch reduces this to 20 milliseconds via an O(clean + dirty)
> > algorithm.
>
>
> I now have a patch that will output the hwv buttons pressed (up,
> down, mute) to a new dynamically allocated misc device as letters
> u, d, m, instead of directly modifying the mixer. Anyone want
> that? It's more flexible than either the patch that's currently
> in -ac or Lukas's patch, but
Mike Galbraith wrote:
>
> On Thu, 7 Jun 2001, watermodem wrote:
>
> > "David S. Miller" wrote:
> > >
> > > George Bonser writes:
> > > > There is, of course, one basic problem with that argument. While you can say
> > > > (and probably rightly so) that such a change would not be included in
On Sat, 9 Jun 2001, Linus Torvalds wrote:
> On Sat, 9 Jun 2001, Alexander Viro wrote:
> >
> > True, but... I can easily see the situation when ->foo() and ->bar()
> > both call a helper function which needs BKL for a small piece of code.
>
> I'd hope that we can fix the small helper
Alan Cox <[EMAIL PROTECTED]> writes:
> > this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
> > It enables the hardware volume control feature of the maestro.
>
> it doesnt apply to the current version of the maestro driver (2.4.5-ac)
> however. I think it is clashing with
On Sat, 9 Jun 2001, Alexander Viro wrote:
>
> True, but... I can easily see the situation when ->foo() and ->bar()
> both call a helper function which needs BKL for a small piece of code.
I'd hope that we can fix the small helper functions to not need BKL -
there are already many circumstances
In article <[EMAIL PROTECTED]>,
David Woodhouse <[EMAIL PROTECTED]> wrote:
>
>Obtaining a read lock twice can deadlock too, can't it?
If it does (with spinlocks), then that's an implementation bug (which
might well be there). We depend on the read-lock being recursive in a
lot of places,
>Bulent,
>
>Could you please check if 2.4.6-pre2+the schedule patch has better
>swapoff behaviour for you?
Marcelo,
It works as expected. Doesn't lockup the box however swapoff keeps burning
the CPU cycles. It took 4 1/2 minutes to swapoff about 256MB of swap
content. Shutdown took just
Hello!
I have a notebook with this sis 7001 usb-controller and sis 630
chipset.(shared memory 8mb), motherboard uniwill 340s2.
Kernel 2.2.x 2.4.1 -2.4.5
X-winows 3.x -4x.
Many low-cost notebooks have this chipset.
All works fine, like my usb-webcam, usb-scanner and my usb-zip-drive with
On Sat, 9 Jun 2001, Linus Torvalds wrote:
> Anyway, in a 2.5.x timeframe we should probably make sure that we do not
> have the need for a recursive BKL any more. That shouldn't be that hard to
> fix, especially with help from CHECKER to verify that we didn't forget
> some case.
True, but...
Go to gkernel on sourceforge or to Andrew Morton's WWW site:
http://www.uow.edu.au/~andrewm/linux/ext3/
On Sat, 9 Jun 2001, P.A.M. van Dam wrote:
> On Fri, Jun 08, 2001 at 03:23:16PM -0600, Peter J. Braam wrote:
> > Hi,
> >
> > Mostly for my own use, I prepared two kernel RPM's with Ext3 in
[EMAIL PROTECTED] said:
> Good point. Spinlocks (with the exception of read-read locks, of
> course) and semaphores will deadlock on recursive use, while the BKL
> has this "process usage counter" recursion protection.
Obtaining a read lock twice can deadlock too, can't it?
A
> this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
> It enables the hardware volume control feature of the maestro.
it doesnt apply to the current version of the maestro driver (2.4.5-ac)
however. I think it is clashing with the docking station support
-
To unsubscribe
On Sat, 9 Jun 2001, Alexander Viro wrote:
>
> Another difference from spinlocks is that BKL is recursive. I'm
> actually surprised that it didn't show up first.
Good point. Spinlocks (with the exception of read-read locks, of course)
and semaphores will deadlock on recursive use, while the BKL
On Mon, Jun 04, 2001 at 08:20:01AM -0400, Hank Leininger wrote:
> On 2001-06-03, Dawson Engler <[EMAIL PROTECTED]> wrote:
>
> > Additionally, do people have suggestions for good security rules?
> > We're looking to expand our security checkers. Right now we just have
> > checkers that warn
> below is the version with the suggested fixes, and with s/hwv/hwvol/ for
> hwv_input also.
fantastic, thanks lukas.
alan, can you throw this in -ac? I don't think it will cause problems
for people with nonstandard wiring on the hw vol pins (read: dell
lattitudes), but if it does we can
On Sat, Jun 09, 2001 at 06:14:24AM -0700, David Brownell wrote:
> Then whatever sets up your ServerWorks ServerSet III LE chipset
> needs its PCI IRQ setup fixed ... I'm not sure how to do this.
>
> Perhaps someone who's familiar with arch/i386/kernel/pci-*.c
> irq setup can suggest the right
On Sat, 9 Jun 2001 11:13:46 -0700,
Wayne Whitney <[EMAIL PROTECTED]> wrote:
>I have verified that the versioning of the do_softirq symbol above is
>the source of the problems in 2.4.6-pre2
Resend, the first patch never appeared. The problem is the call to
do_softirq inside an asm string where
I am using linux-2.2.19 and I have a problem with irq handling:
if some program requests an irq and doesn't free it before exit, I have to
reboot my machine in order to make this program to work again.
I mean dosemu: if it crashes, it doesn't handle irqs any more until reboot.
I can demonstrate
> > By giving hwv=0 to insmod one can explicitly disable it. Setting
>
> can we have a better name like 'hwvol_enable'?
>
> > + set_mixer(c, 0, val);
>
> careful. you just used the indirect ac97 registers without holding the
> card's lock.. if another processor does a mixer ioctl
Hi there.
A friend of mine is having a problem with the 2.2.19 kernel on one of
his boxes, and has asked for some advice which is beyond my experience
so I'm asking here: Is this a kernel problem or something else?
First, the hardware, as best we can determine:
Vesa VLB motherboard,
Hi All,
I get this panic running RedHat 2.4.3-6:
Unable to handle kernel NULL pointer dereference at virtual address 0004
c014b13d
Oops: 0002
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: ebx: c4a6dcc0 ecx: c4a6dce8 edx:
I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results. Everything boots
great and I can login fine. When I try to assign an IP via DHCP or ifconfig, the
system
sits and stares at me indefinitely. 2.4.5-pre4 didn't compile for me, but pre3 works
fine
and pre5 locks. There is
On 9 Jun 2001, Linus Torvalds wrote:
> The big kernel lock rules are that it's a "normal spinlock" in many
> regards, BUT you can block while holding it, and the BKL will magically
> be released during the blocking. This means, for example, that the BKL
> can never deadlock with a semaphore -
> takes 45 seconds CPU time due to the O(clean * dirty) algorithm in
> truncate_inode_pages(). The machine is locked up for the duration.
> The patch reduces this to 20 milliseconds via an O(clean + dirty)
> algorithm.
Unfortunately, it's _not_ O(clean + dirty).
> + while
In article <[EMAIL PROTECTED]>,
Dawson Engler <[EMAIL PROTECTED]> wrote:
>
>we're starting to develop a checker that finds deadlocks by (1)
>computing all lock acquisition paths and (2) checking if two paths
>violate a partial order.
Looks good.
>The checker is pretty primitive. In
Hi,
> I haven't encountered any CPU with builtin temperature sensors.
Well, I've got an Apple iMac (tee hee hee) with a PowerPC G3 (or 750 for you
number guys). I know for sure that all of the G3 / G4 chips have
temperature sensors built onto the CPU core.
Mine's showing 23 degrees Celsius at
> this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
> It enables the hardware volume control feature of the maestro.
cool. I had support for this in the mega-patch I posted long ago, but
I never seperated and submitted those changes 'cause I'm a moron.
> By giving hwv=0 to
Hi,
this patch applies to (at least) 2.4.3 up to and including 2.4.6-pre2.
It enables the hardware volume control feature of the maestro.
By giving hwv=0 to insmod one can explicitly disable it. Setting
hwv_input=1 requests the alternative HWV input pins to be used.
The maestro will generate
"P.A.M. van Dam" wrote:
>
> On Fri, Jun 08, 2001 at 03:23:16PM -0600, Peter J. Braam wrote:
> > Hi,
> >
> > Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.
> >
> > Versions:
> > 2.2.19 + 0.0.7a
> > 2.4.5 + 0.0.6
> >
> > PLEASE USE THESE AT YOUR OWN RISK - THEY CONTAIN
On Fri, Jun 08, 2001 at 03:23:16PM -0600, Peter J. Braam wrote:
> Hi,
>
> Mostly for my own use, I prepared two kernel RPM's with Ext3 in them.
>
> Versions:
> 2.2.19 + 0.0.7a
> 2.4.5 + 0.0.6
>
> PLEASE USE THESE AT YOUR OWN RISK - THEY CONTAIN EXPERIMENTAL FILE SYSTEM
> CODE.
> - Peter J.
"Mathiasen, Torben" wrote:
>
> Paulo,
>
> Thanks for the update/patch. Sorry I missed your first email, bu I've been
> way too busy with other stuff the last couple of months.
Thank Hollis. :-) As I've already said, I'm really no kernel hacker.
OTOH I've programmed a lot 5+ years ago, so I can
On Sat, 9 Jun 2001 11:07:52 -0400,
Ed Tomlinson <[EMAIL PROTECTED]> wrote:
>Built -pre2 and noticed most of the modules in net/* are getting
>a missing symbol for do_softirq.
http://www.tux.org/lkml/#s8-8
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Hi,
Just updated to 2.4.5 from 2.2.18 and there seems to be a difference in the OPL3-SA2
sound driver.
I have an Intel AL440LX motherboard with onboard sound, after setting up the sound
driver under 2.4.5 I get a strange effect when trying to play any sound files; the
files play very slow
The ftruncate() in this program:
#include
#include
#include
int clean = 64 * 1024 * 1024;
int dirty = 64 * 1024 * 1024;
main()
{
int fd = open("foo", O_RDWR|O_TRUNC|O_CREAT, 0666);
void *mem;
ftruncate(fd, clean + dirty);
mem = mmap(0, clean + dirty,
Hi,
Built -pre2 and noticed most of the modules in net/* are getting
a missing symbol for do_softirq.
Have I messed up, or is there a real error?
Ed Tomlinson <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
James Sutherland <[EMAIL PROTECTED]> wrote:
>
> The current x86 setup uses a small sensor sitting under the CPU socket.
Current Intel chips have a sensor built right into the die of the processor
itself -- voila, close enough to the critical junction temperature for any
purpose. Many
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi there!
I am trying to install Linux 2.4.4 on the new Toshiba
Libretto, the one with the Crusoe CPU, 1280x600 screen,
1kg (I think it is currently only sold in Japan).
I am having problems with IRQs and the recognition of
system components,
ftp://ftp.kernel.org/pub/linux/kernel/people/alan/2.4/
Intermediate diffs are available from
http://www.bzimage.org
In terms of going through the code audit almost all the sound drivers still
need fixing to lock against format changes during a
Mike Galbraith <[EMAIL PROTECTED]> writes:
> On Fri, 8 Jun 2001, John Stoffel wrote:
>
> > Mike> OK, riddle me this. If this test is a crummy test, just how is
> > Mike> it that I was able to warn Rik in advance that when 2.4.5 was
> > Mike> released, he should expect complaints? How did I
>A panic occurs at boot while the aic7xxx is doing its thing..the
>following has been hand copied from the screen...
Unfortunately, this trace is somewhat useless. Without symbol
references, it is impossible to say where the panic occurred
or where (symbol location is highly dependent on how
On Sat, Jun 09, 2001 at 02:06:45PM +0200, Trond Myklebust wrote:
> > " " == Ian Lynagh <[EMAIL PROTECTED]> writes:
>
> > When trying to mount something over NFS with a 2.2.19 kernel we
> > get:
>
> > Unsupported unaligned load/store trap for kernel at
> >
> " " == Ian Lynagh <[EMAIL PROTECTED]> writes:
> Hi all
> We have a sun ultra 1 with /proc/cpuinfo as follows:
> cpu : TI UltraSparc I (SpitFire) fpu : UltraSparc I integrated
> FPU promlib : Version 3 Revision 1 prom : 3.1.1 type : sun4u
> ncpus probed : 1 ncpus
On Sat, 9 Jun 2001, Dawson Engler wrote:
> Hi All,
>
> we're starting to develop a checker that finds deadlocks by (1)
> computing all lock acquisition paths and (2) checking if two paths
> violate a partial order.
>
> E.g., for two threads T1 and T2:
> T1: foo acquires A --> calls bar
Hi all
We have a sun ultra 1 with /proc/cpuinfo as follows:
cpu : TI UltraSparc I (SpitFire)
fpu : UltraSparc I integrated FPU
promlib : Version 3 Revision 1
prom: 3.1.1
type: sun4u
ncpus probed: 1
ncpus active: 1
BogoMips
Paulo Afonso Graner Fessel wrote:
> [...]
> He said me that these funtions don't address the endianess question, and
> sent me a patch. He said that this probably wouldn't work, but I've
> decided to give a try anyway. Here is the patch:
>
> --- tlan.c.old Thu Jun 7 21:24:25 2001
> +++
"L. K." wrote:
> I haven't encountered any CPU with builtin temperature sensors.
>
Eh, all Pentium class cpus have a build in sensor for core temperature (I believe
Athlons
too). It's just the logic which is outside in form of a A/D converter connected to a
I2C
bus.
Regards,
--
Steffen
On Fri, Jun 08, 2001 at 06:08:46PM +0200, Maciej W. Rozycki wrote:
> Still it has two loops...
Ok, here is a single loop version.
Ivan.
--- 2.4.5-ac11/mm/mmap.cFri Jun 8 15:59:35 2001
+++ linux/mm/mmap.c Sat Jun 9 12:50:05 2001
@@ -398,27 +398,37 @@ free_vma:
static inline
On 8 Jun 2001, Bill Pringlemeir wrote:
>
> > "MHW" == Michael H Warfield <[EMAIL PROTECTED]> writes:
> [snip]
> MHW> Yes, bits are free, sort of... That's why an extra decimal
> MHW> place is "ok". Keeping precision within an order of magnitude
> MHW> of accuracy is within
Paulo,
Thanks for the update/patch. Sorry I missed your first email, bu I've been
way too busy with other stuff the last couple of months.
There's a lot of endianess issues in the tlan driver, but none really
bothered fixing them. No one really assumed the tlan adapters would be used
on
> > From: L. K. [mailto:[EMAIL PROTECTED]]
> > I really do not belive that for a CPU or a motherboard +- 1
> > degree would make any difference.
>
> You haven't pushed your system, or run it in a hostile
> environment then. There are many places where systems are run
> right up to the edge of
On 9 Jun 2001, H. Peter Anvin wrote:
> Followup to: <[EMAIL PROTECTED]>
> By author:"Albert D. Cahalan" <[EMAIL PROTECTED]>
> In newsgroup: linux.dev.kernel
> > >
> > > But in spite of all this, you're not really measure the critical
> > > temperature, which is junction tempature. Yes, case
We had for an hour or so a bad intermediate diff
going from kernel 2.4.5-ac9 to ac10.
The size of the patch was 800+ kilobyte.
The new "good" one is about 163 kilobyte.
If you try to apply the wrong patch, it complains
about scsidrivers beeing reversed.
Sorry for the troubles.
Danny
--
On Fri, Jun 08, 2001 at 03:19:46PM -0500, Mike Coleman wrote:
> Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> > > Can't it make mouse jump forward and back when user suddenly stops?
> >
> > In theory - yes. It doesn't seem to be a problem in practice, though.
> > It'll happen when a user slows
On Sat, 9 Jun 2001, Rik van Riel wrote:
>> Why are half the people here trying to hide behind this diskspace
>> is cheap argument? If we rely on that, then Linux sucks shit.
>
>Never mind them, I haven't seen any of them contribute
>VM code, even ;)
Nor have I, but I think you guys working on
Followup to: <[EMAIL PROTECTED]>
By author:"Albert D. Cahalan" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> I hope you don't think people would assume that a "float" always
> has useful data in all 23 fraction bits. It is a similar case.
>
> So here you go, a kernel-safe
On Wed, 6 Jun 2001, Mike A. Harris wrote:
> Why are half the people here trying to hide behind this diskspace
> is cheap argument? If we rely on that, then Linux sucks shit.
Never mind them, I haven't seen any of them contribute
VM code, even ;)
OTOH, disk space _is_ cheap, so the other VM -
Michael H. Warfiel writes:
> On Fri, Jun 08, 2001 at 05:16:39PM -0400, Albert D. Cahalan wrote:
>> The bits are free; the API is hard to change.
>> Sensors might get better, at least on high-end systems.
>> Rounding gives a constant 0.15 degree error.
>> Only the truly stupid would assume
Followup to: <[EMAIL PROTECTED]>
By author:"Albert D. Cahalan" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
> >
> > But in spite of all this, you're not really measure the critical
> > temperature, which is junction tempature. Yes, case tempature has *some*
>
> There are processors
Struct padding is a problem. Really, there shouldn't be any
implicit padding. This causes:
1. security leaks when such structs are copied to userspace
(the implicit padding is uninitialized, and so may contain
a chunk of somebody's private key or password)
2. bloat, when struct members
Hi All,
we're starting to develop a checker that finds deadlocks by (1)
computing all lock acquisition paths and (2) checking if two paths
violate a partial order.
E.g., for two threads T1 and T2:
T1: foo acquires A --> calls bar which tries to acquire B
T2: baz acquires B -->
Followup to: <[EMAIL PROTECTED]>
By author:Chris Boot <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Well then, tell all the teachers in this world that they're stupid, and tell
> everyone who learnt from them as well. I'm in high school (gd. 11, junior)
> and my physics teacher is
Followup to: <[EMAIL PROTECTED]>
By author:"Michael H. Warfield" <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
>
> Yes, bits are free, sort of... That's why an extra decimal
> place is "ok". Keeping precision within an order of magnitude of
> accuracy is within the realm of
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 in an entirely unresponsive state, while 2.2 handles
On Wed, 6 Jun 2001, Derek Glidden wrote:
> Or are you saying that if someone is unhappy with a particular
> situation, they should just keep their mouth shut and accept it?
There are lots of options ...
1) wait until somebody fixes the problem
2) fix the problem yourself
3) start infinite
On Wed, 6 Jun 2001, Sean Hunter wrote:
> A working VM would have several differences from what we have in my
> opinion, among which are:
> - It wouldn't require 8GB of swap on my large boxes
> - It wouldn't suffer from the "bounce buffer" bug on my
> large boxes
>
Is running without swap a possible workaround for all this vm weirdness
folks are reporting?
Alexander
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
> reads the RTC device. The patched RTC driver can then
> measure the elapsed time between the interrupt and the
> read from userspace. Voila: latency.
interesting, but I'm not sure there's much advantage over
doing it entirely in user-space with the normal /dev/rtc:
reads the RTC device. The patched RTC driver can then
measure the elapsed time between the interrupt and the
read from userspace. Voila: latency.
interesting, but I'm not sure there's much advantage over
doing it entirely in user-space with the normal /dev/rtc:
Is running without swap a possible workaround for all this vm weirdness
folks are reporting?
Alexander
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
On Wed, 6 Jun 2001, Sean Hunter wrote:
A working VM would have several differences from what we have in my
opinion, among which are:
- It wouldn't require 8GB of swap on my large boxes
- It wouldn't suffer from the bounce buffer bug on my
large boxes
- It
On Wed, 6 Jun 2001, Derek Glidden wrote:
Or are you saying that if someone is unhappy with a particular
situation, they should just keep their mouth shut and accept it?
There are lots of options ...
1) wait until somebody fixes the problem
2) fix the problem yourself
3) start infinite
Followup to: [EMAIL PROTECTED]
By author:Michael H. Warfield [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Yes, bits are free, sort of... That's why an extra decimal
place is ok. Keeping precision within an order of magnitude of
accuracy is within the realm of reasonable.
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 in an entirely unresponsive state, while 2.2 handles identical
Followup to: [EMAIL PROTECTED]
By author:Chris Boot [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
Well then, tell all the teachers in this world that they're stupid, and tell
everyone who learnt from them as well. I'm in high school (gd. 11, junior)
and my physics teacher is always
Struct padding is a problem. Really, there shouldn't be any
implicit padding. This causes:
1. security leaks when such structs are copied to userspace
(the implicit padding is uninitialized, and so may contain
a chunk of somebody's private key or password)
2. bloat, when struct members
Hi All,
we're starting to develop a checker that finds deadlocks by (1)
computing all lock acquisition paths and (2) checking if two paths
violate a partial order.
E.g., for two threads T1 and T2:
T1: foo acquires A -- calls bar which tries to acquire B
T2: baz acquires B --
Michael H. Warfiel writes:
On Fri, Jun 08, 2001 at 05:16:39PM -0400, Albert D. Cahalan wrote:
The bits are free; the API is hard to change.
Sensors might get better, at least on high-end systems.
Rounding gives a constant 0.15 degree error.
Only the truly stupid would assume accuracy from
Followup to: [EMAIL PROTECTED]
By author:Albert D. Cahalan [EMAIL PROTECTED]
In newsgroup: linux.dev.kernel
But in spite of all this, you're not really measure the critical
temperature, which is junction tempature. Yes, case tempature has *some*
There are processors with
On Wed, 6 Jun 2001, Mike A. Harris wrote:
Why are half the people here trying to hide behind this diskspace
is cheap argument? If we rely on that, then Linux sucks shit.
Never mind them, I haven't seen any of them contribute
VM code, even ;)
OTOH, disk space _is_ cheap, so the other VM -
1 - 100 of 176 matches
Mail list logo
