On Wednesday 17 January 2007 16:10, Matheus Izvekov wrote:
> On 1/17/07, Len Brown <[EMAIL PROTECTED]> wrote:
> > The code that enables ACPI mode hasn't really changed since before 2.6.12 --
> > unless udelay() has changed beneath us...
> > So if you are going to test an old version of Linux, you s
Alex Dubov wrote:
> Greetings.
>
> It appears to me that under certain circumstances mmc layer will issue
> requests to the host after
> mmc_host_remove returns. This happens, for example, in tifm_sd driver because
> mmc_host may be
> removed mid-transfer, as the socket shall be freed for possibl
Hugh Dickins wrote:
On Thu, 18 Jan 2007, Nadia Derbey wrote:
Trying to mmap /dev/kmem with an offset I take from /boot/System.map,
I get an EIO error on a 2.6.20-rc4.
This is something that used to work on older kernels.
Had a look at mmap_kmem() in drivers/char/mem.c, and I'm wondering whethe
Hi!
> > > Especially the PCI video_state trick finally got me a working resume on
> > > 2.6.19-ck2 r128 Rage Mobility M4 AGP *WITH*(!) fully enabled and working
> > > (and keeping working!) DRI (3D).
> >
> > Can we get whitelist entry for suspend.sf.net? s2ram from there can do
> > all the tricks
Hi!
> This patch adds support for PM_TRACE for the x86_64 architecture. Thanks
> to Linus for help with my asm ignorance.
>
> Please apply.
>
> Signed-off-by: Nigel Cunningham <[EMAIL PROTECTED]>
Ack, looks nice to me. i386 code does not belong to generic headers,
anyway...
Juergen Pfeiffer schrieb:
I had problems in my implementation of Profibus-protocol, because my
FDL-State machine is implemented in tasklets and
sometimes there were situations, where Soft-Irqs were disabled for
20-40mS (Coldfire 5485 / 96MHz).
After inserting some testpoints in kernels source,
On Thu, 2007-01-18 at 10:49 -0500, Trond Myklebust wrote:
> After the dirty page has been written to unstable storage, it marks the
> inode using I_DIRTY_DATASYNC, which should then ensure that the VFS
> calls write_inode() on the next pass through __sync_single_inode.
> I'd rather like to see fs
linux-os (Dick Johnson) wrote:
Sometimes a idiot boss will say; "You need to read or write files from
within the driver. If you don't do what I tell you, you are fired!"
To which the response is something like
"This is impossible/illegal/unsupported so it can't be done."
Fortunately, civiliz
Raz Ben-Jehuda(caro) wrote:
3. In 64bit machines , is it possible to allocate huge buffers , such
as 30 GB of ram ?
Yes, that is one of the nice things about 64-bit machines.
No special cases - you sure can get 30GB if your machine
is equipped with that much. Or you can get that
much virtual m
please fix the comment as well.
oops number is very helpful in dealing with people
reports. Very often the first Oops is required to get
understanding of the real problem, so
further oops can be ignored and the first one requested
if the problem is reproducable.
Kirill
> From: Pavel Emelianov <
[RFC][PATCH] Power S3 Resume optimisation
Here is a simple patch for optimising the S3 resume. With this
patch the resume time is 0.85. Given the fact that device initialisation
on the resume takes almost 70% of time, By executing the whole
"device_resume()" function on a seperate kernel t
On 1/15/07, Raz Ben-Jehuda(caro) <[EMAIL PROTECTED]> wrote:
I have a process who allocates as much as possible of RAM
in 4 G ram 32bit machine. This buffer is never released.
Questions:
1. Is it better allocates with many 1MB buffers or allocate it in with
one a big valloc ?
ONe BIG vmalloc
On 1/18/07, Michael Halcrow <[EMAIL PROTECTED]> wrote:
+ page_data = (char *)kmap_atomic(page, KM_USER0);
+ lower_page_data = (char *)kmap_atomic(lower_page, KM_USER1);
Drop 'em redundant casts, please.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
apologies if this is an inappropriately trivial question but this
has been bugging me for a while. what is the deal with "inline"?
first, there appear to be three possible ways of specifying an
inline routine in the kernel source:
$ grep -r "static inline " .
$ grep -r "static __inline_
> "Condor" <[EMAIL PROTECTED]> writes:
>
>> I no longer can make tests because i remove my fat32 from my usb stick
>> and
>> i put it in to FAT16 and i make the exact tests and file is worked but
>> on
>> fat16 not in fat32. I just report the problem, to be investigate from
>> kernel developers.
>
* Russell King <[EMAIL PROTECTED]> [2007-01-18 16:23]:
>
> However, there is a bigger question here: that is the tradeoff between
> making this variable part of the on-disk kernel image, but throw away
> the memory at runtime, or to leave it in the BSS where it will not be
> part of the on-disk ke
On 1/19/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
is there a simple explanation for how to *properly* define inline
routines in the kernel? and maybe this can be added to the
CodingStyle guide (he mused, wistfully).
AFAIK __always_inline is the only reliable way to force inlining where
i
On Fri, 2007-01-19 at 10:34 +0100, Peter Zijlstra wrote:
> On Thu, 2007-01-18 at 10:49 -0500, Trond Myklebust wrote:
>
> > After the dirty page has been written to unstable storage, it marks the
> > inode using I_DIRTY_DATASYNC, which should then ensure that the VFS
> > calls write_inode() on the
On Fri, 19 Jan 2007, Pekka Enberg wrote:
> On 1/19/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > is there a simple explanation for how to *properly* define inline
> > routines in the kernel? and maybe this can be added to the
> > CodingStyle guide (he mused, wistfully).
>
> AFAIK __always_i
"Robert P. J. Day" <[EMAIL PROTECTED]> writes:
> first, there appear to be three possible ways of specifying an
> inline routine in the kernel source:
>
> $ grep -r "static inline " .
> $ grep -r "static __inline__ " .
> $ grep -r "static __inline " .
>
> i vaguely recall that this has som
Hi,
Hugh Dickins wrote:
On Thu, 18 Jan 2007, Nadia Derbey wrote:
Trying to mmap /dev/kmem with an offset I take from /boot/System.map,
I get an EIO error on a 2.6.20-rc4.
This is something that used to work on older kernels.
Had a look at mmap_kmem() in drivers/char/mem.c, and I'm wondering wh
On Fri, 19 Jan 2007, Andreas Schwab wrote:
> "Robert P. J. Day" <[EMAIL PROTECTED]> writes:
>
> > first, there appear to be three possible ways of specifying an
> > inline routine in the kernel source:
> >
> > $ grep -r "static inline " .
> > $ grep -r "static __inline__ " .
> > $ grep -r
"Robert P. J. Day" <[EMAIL PROTECTED]> writes:
> but in terms of strict C89 compatibility, it would seem to be a bit
> late for that given:
>
> $ grep -r "static inline " .
>
> no?
The kernel does not use strict C89, it uses GNUC89.
Andreas.
--
Andreas Schwab, SuSE Labs, [EMAIL PROTECTED]
Su
On Thu, 2007-01-18 at 19:26 +0300, Alexey Dobriyan wrote:
> Martin, are you OK with comments tweaking in s390 code?
> -
> [PATCH 1/2] Consolidate bust_spinlocks()
Yes, this should be fine now.
--
blue skies,
Martin.
Martin Schwidefsky
Linux for zSeries
On Fri, Jan 19, 2007 at 03:01:44PM +0200, Pekka Enberg wrote:
> On 1/19/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> >is there a simple explanation for how to *properly* define inline
> >routines in the kernel? and maybe this can be added to the
> >CodingStyle guide (he mused, wistfully).
>
On Fri, 19 Jan 2007, Andreas Schwab wrote:
> "Robert P. J. Day" <[EMAIL PROTECTED]> writes:
>
> > but in terms of strict C89 compatibility, it would seem to be a bit
> > late for that given:
> >
> > $ grep -r "static inline " .
> >
> > no?
>
> The kernel does not use strict C89, it uses GNUC89.
Aubrey Li wrote:
> Here is the newest patch against 2.6.20-rc5.
> ==
> From ad9ca9a32bdcaddce9988afbf0187bfd04685a0c Mon Sep 17 00:00:00 2001
> From: Aubrey.Li <[EMAIL PROTECTED]>
> Date: Thu, 18 Jan 2007 11:08:31 +0800
> Subject: [PATCH] Add an
Arjan van de Ven <[EMAIL PROTECTED]> writes:
On Thu, 2007-01-18 at 20:29 +0100, Alessandro Di Marco wrote:
> Hi all,
>
> this is a new 2.6.20 module implementing a user inactivity trigger.
Basically
> it acts as an event sniffer, issuing an ACPI event when no user activity is
>
On Fri, 19 Jan 2007, Adrian Bunk wrote:
> On Fri, Jan 19, 2007 at 03:01:44PM +0200, Pekka Enberg wrote:
> > On 1/19/07, Robert P. J. Day <[EMAIL PROTECTED]> wrote:
> > >is there a simple explanation for how to *properly* define inline
> > >routines in the kernel? and maybe this can be added to th
On Tuesday 16 January 2007 00:34, Robert Hancock wrote:
> I'll try your stress test when I get a chance, but I doubt I'll run into
> the same problem and I haven't seen any similar reports. Perhaps it's
> some kind of wierd timing issue or incompatibility between the
> controller and that drive whe
Aubrey Li wrote:
> Here is the newest patch against 2.6.20-rc5.
> ==
> From ad9ca9a32bdcaddce9988afbf0187bfd04685a0c Mon Sep 17 00:00:00 2001
> From: Aubrey.Li <[EMAIL PROTECTED]>
> Date: Thu, 18 Jan 2007 11:08:31 +0800
> Subject: [PATCH] Add an
Hi,
On some ARM platform with multiple pci bridges, I had to add the below
patch in order to enable transactions through the bridges to devices
behind. I'm sure there are other platforms with similar pci setup so
why wouldn't it work without it?
Thanks,
Bahadir
Enable bus transactions behind br
On Fri, 19 Jan 2007, Adrian Bunk wrote:
> With the current implementation in the kernel (and considering that
> CONFIG_FORCED_INLINING was implemented in a way that it never had
> any effect), __always_inline and inline are currently equivalent.
yes, that option was implemented in a half-assed so
On Tuesday 16 January 2007 01:53, Jeff Garzik wrote:
> Robert Hancock wrote:
> > I'll try your stress test when I get a chance, but I doubt I'll run into
> > the same problem and I haven't seen any similar reports. Perhaps it's
> > some kind of wierd timing issue or incompatibility between the
> >
On Fri, 2007-01-19 at 09:19 +0530, Vivek Goyal wrote:
> On Thu, Jan 18, 2007 at 02:13:39PM -0500, Benjamin Romer wrote:
> [..]
> > > >
> > > > OK, here's the updated patch that uses the new definition and fixes up
> > > > the other places that use it. I built and tested this on the ES7000/ONE
> > >
On 1/19/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
Hi Aubrey,
I used your patch on my PPC64 box and I do not get expected
behavior. As you had requested, I am attaching zoneinfo and meminfo
dumps:
Please let me know if you need any further data to help me out with
the test/experim
Hello,
I just tried my shiny new usb extension cable (repeater):
Jan 19 16:01:17 epia kernel: usb 5-1: new high speed USB device using
ehci_hcd and address 60
Jan 19 16:01:17 epia kernel: usb 5-1: configuration #1 chosen from 1 choice
Jan 19 16:01:17 epia kernel: hub 5-1:1.0: USB hub found
Jan 19
On Fri, 19 Jan 2007 10:11:10 -0500 Benjamin Romer wrote:
> On Fri, 2007-01-19 at 09:19 +0530, Vivek Goyal wrote:
> > On Thu, Jan 18, 2007 at 02:13:39PM -0500, Benjamin Romer wrote:
> > [..]
> > > > >
> > > > > OK, here's the updated patch that uses the new definition and fixes up
> > > > > the oth
Benjamin Romer <[EMAIL PROTECTED]> writes:
> On Fri, 2007-01-19 at 09:19 +0530, Vivek Goyal wrote:
>> On Thu, Jan 18, 2007 at 02:13:39PM -0500, Benjamin Romer wrote:
>> [..]
>> > > >
>> > > > OK, here's the updated patch that uses the new definition and fixes up
>> > > > the other places that use
On 1/19/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
Hi Aubrey,
The idea of creating separate flag for pagecache in page_alloc is
interesting. The good part is that you flag watermark low and the
zone reclaimer will do the rest of the job.
However when the zone reclaimer starts to
"Condor" <[EMAIL PROTECTED]> writes:
>>From debug log:
> Jan 16 14:56:13 elrond kernel: usb-storage: device found at 4
> Jan 16 14:56:13 elrond kernel: usb-storage: waiting for device to settle
> before scanning
> Jan 16 14:56:18 elrond kernel: sda: Mode Sense: 00 00 00 00
> Jan 16 14:56:18 elrond
On Mon, Dec 18, 2006 at 10:53:43PM +, Christoph Hellwig wrote:
> On Mon, Dec 18, 2006 at 05:21:09PM -0500, Ed L. Cashin wrote:
...
> > If anyone has a better reference, I'd like to see it.
>
> I searched around a little bit and found these:
>
>
> http://groups.google.at/group/open-iscs
From: Alexey Kuznetsov <[EMAIL PROTECTED]>
If read failed we cannot map not-uptodate page to user space.
Actually, we are in serious troubles, we do not even know what
process to kill. So, the only variant remains: to stop swapoff()
and allow someone to kill processes to zap invalid pages.
Signed
On Fri, 19 Jan 2007, Nadia Derbey wrote:
> Hugh Dickins wrote:
> >
> > Sigh, you're right, 2.6.19 messed that up completely.
> > No, you never had to subtract PAGE_OFFSET from that address
> > in the past, and you shouldn't have to do so now.
Whoops, I should never have said "never". Checking fu
Robert Hancock wrote:
Orion Poplawski wrote:
Can someone please explain to me what these mean?
EDAC k8 MC1: general bus error: participating processor(local node
origin), time-out(no timeout) memory transaction type(generic read),
mem or i/o(mem access), cache level(generic)
EDAC MC1: CE page
On Fri, 2007-01-19 at 14:07 +0100, Peter Zijlstra wrote:
> On Fri, 2007-01-19 at 10:34 +0100, Peter Zijlstra wrote:
> > On Thu, 2007-01-18 at 10:49 -0500, Trond Myklebust wrote:
> >
> > > After the dirty page has been written to unstable storage, it marks the
> > > inode using I_DIRTY_DATASYNC, wh
On Fri, 2007-01-19 at 16:33 +, Hugh Dickins wrote:
> Though I do wonder whether
> it was safe to change its behaviour at that stage: more evidence that
> few have actually been using mmap of /dev/kmem.
... and maybe we should just kill /dev/kmem entirely... it seems mostly
used by rootkits bu
On Fri, 19 Jan 2007, Franck Bui-Huu wrote:
> Hugh Dickins wrote:
> >
> > Please revert the offending patch below, and then maybe Franck
> > can come up with a patch which preserves the original behaviour
> > on architectures which used to work (e.g. i386), while fixing
> > it for those architecture
Remove the macros that define simple "inlining" to mean forced
inlining, since you can (and *should*) get that effect with the
CONFIG_FORCED_INLINING kernel config variable instead.
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
this change was compile tested on x86 with "make ally
Hello.
Bartlomiej Zolnierkiewicz wrote:
[PATCH] ide: update MAINTAINERS entry
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL PROTECTED]>
---
MAINTAINERS |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
Index: my-2.6/MAINTAINERS
Hello.
Bartlomiej Zolnierkiewicz wrote:
[PATCH] ide: disable DMA in ->ide_dma_check for "no IORDY" case
I've looked thru the code, and found more issues with the PIO fallback
there. Will try to cook up patches for at least some drivers...
Signed-off-by: Bartlomiej Zolnierkiewicz <[EMAIL
Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
> Hi,
>
> I can't scan anymore. :-( I don't know which rc kernel introduced it, but
> this
> are the messages I get (w/o touching the device/usb cable except pluggin it
> in for the first time):
Hi,
I need "lsusb -v" for your devic
Am Freitag 19 Januar 2007 12:29 schrieb Oliver Neukum:
> Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
> > Hi,
> >
> > I can't scan anymore. :-( I don't know which rc kernel introduced it, but
> > this are the messages I get (w/o touching the device/usb cable except
> > pluggin it i
> Am Donnerstag, 11. Januar 2007 18:20 schrieb Prakash Punnoor:
> > Hi,
> >
> > I can't scan anymore. :-( I don't know which rc kernel introduced it, but
> > this are the messages I get (w/o touching the device/usb cable except
> > pluggin it in for the first time):
>
Hi,
I found quickly booted in
On Fri, 19 Jan 2007, Arjan van de Ven wrote:
> On Fri, 2007-01-19 at 16:33 +, Hugh Dickins wrote:
> > Though I do wonder whether
> > it was safe to change its behaviour at that stage: more evidence that
> > few have actually been using mmap of /dev/kmem.
>
> ... and maybe we should just kill
On the Unisys ES7000/ONE system, we encountered a problem where
performing a kexec reboot or dump on any cell other than cell 0 causes
the system timer to stop working, resulting in a hang during timer
calibration in the new kernel.
We traced the problem to one line of code in disable_IO_APIC(),
On Fri, 2007-01-19 at 07:43 -0800, Randy Dunlap wrote:
> On Fri, 19 Jan 2007 10:11:10 -0500 Benjamin Romer wrote:
>
> > On Fri, 2007-01-19 at 09:19 +0530, Vivek Goyal wrote:
> > > On Thu, Jan 18, 2007 at 02:13:39PM -0500, Benjamin Romer wrote:
> > > [..]
> > > > > >
> > > > > > OK, here's the upda
On Jan 19, 2007, "Robert P. J. Day" <[EMAIL PROTECTED]> wrote:
> first, there appear to be three possible ways of specifying an
> inline routine in the kernel source:
inline, __inline and __inline__ are equivalent as far as GCC is
concerned, as you've already figured out.
> i vaguely recall th
On Fri, 19 Jan 2007, Peter Zijlstra wrote:
> + /*
> + * NFS congestion size, scale with available memory.
> + *
Well this all depends on the memory available to the running process.
If the process is just allowed to allocate from a subset of memory
(cpusets) then this may need to b
On Fri, Jan 19, 2007 at 11:56:30AM -0500, Robert P. J. Day wrote:
>
> Remove the macros that define simple "inlining" to mean forced
> inlining, since you can (and *should*) get that effect with the
> CONFIG_FORCED_INLINING kernel config variable instead.
NAK.
I don't see any place in the kern
On Fri, 2007-01-19 at 17:12 +, Hugh Dickins wrote:
> On Fri, 19 Jan 2007, Arjan van de Ven wrote:
> > On Fri, 2007-01-19 at 16:33 +, Hugh Dickins wrote:
> > > Though I do wonder whether
> > > it was safe to change its behaviour at that stage: more evidence that
> > > few have actually been
On Fri, Jan 19, 2007 at 03:15:03PM -0200, Alexandre Oliva wrote:
>...
> That's still a long way ahead (the 4.3 development cycle has just
> started), but it wouldn't hurt to start fixing incompatibilities
> sooner rather than later, and coming up with a clean and uniform set
> of inline macros that
[ I believe you wanted LKML and not majordomo, also CC'd Ingo since he's
the maintainer of the -rt patch ]
On Fri, 2007-01-19 at 16:20 +0530, Alim Akhtar wrote:
>
> Dear Steven/Thomas Gleixner
>
> i am using linux.2.6.14 + patch-2.6.14-rt22 for a iMX21 based coustom
> board.
Could you try 2.6.2
On 1/19/07, Alessandro Di Marco <[EMAIL PROTECTED]> wrote:
The patch in attachment fixes some silly bugs of the previous version.
Regards,
Hi, attached is a patch for your gentable file, rewriting some of the
user prompts to make them more readable.
Regards,
scott
--- gentable 2007-01-19 11:
On Fri, 19 Jan 2007, Arjan van de Ven wrote:
> On Fri, 2007-01-19 at 17:12 +, Hugh Dickins wrote:
> > Though so long as /dev/mem support remains, /dev/kmem might as well?
>
> they're not the same; for a long time, /dev/mem on actual memory
> returned zeros... so you couldn't use it for rootkit
On Fri, 19 Jan 2007, Adrian Bunk wrote:
> On Fri, Jan 19, 2007 at 11:56:30AM -0500, Robert P. J. Day wrote:
> >
> > Remove the macros that define simple "inlining" to mean forced
> > inlining, since you can (and *should*) get that effect with the
> > CONFIG_FORCED_INLINING kernel config variable
On Fri, 2007-01-19 at 11:51 -0500, Trond Myklebust wrote:
> > So with that out of the way I now have this
>
> Looks much better. Just one obvious buglet...
> > @@ -1565,6 +1579,23 @@ int __init nfs_init_writepagecache(void)
> > if (nfs_commit_mempool == NULL)
> > return -ENOMEM;
On Fri, 2007-01-19 at 09:20 -0800, Christoph Lameter wrote:
> On Fri, 19 Jan 2007, Peter Zijlstra wrote:
>
> > + /*
> > +* NFS congestion size, scale with available memory.
> > +*
>
> Well this all depends on the memory available to the running process.
> If the process is just allowed
On 1/19/07, Len Brown <[EMAIL PROTECTED]> wrote:
I guess I'm losing my mind, because when I read this code,
there are only two ways out of the while(retry) loop.
Either return with success, or retry is 0.
So how the heck is retry printed as 142?!
did you notice any delay between the last two lin
On Fri, 19 Jan 2007, Peter Zijlstra wrote:
> Eeuh, right. Glad to have you around to remind how puny my boxens
> are :-)
Sorry about that but it was unavoidable if we want to get to reasonable
limits that will work in all situations.
-
To unsubscribe from this list: send the line "unsubscribe l
On Fri, 19 Jan 2007, Alexey Dobriyan wrote:
> From: Alexey Kuznetsov <[EMAIL PROTECTED]>
>
> If read failed we cannot map not-uptodate page to user space.
Good point.
> Actually, we are in serious troubles, we do not even know what
> process to kill.
True, though we don't really want to kill a
Hi Andrew,
Thanks again for finding the fix to the problem I reported.
Can you tell me when I might expect this fix to show up in
2.6.20-rc?
Thanks,
Mike
Andrew Morton wrote:
> On Thu, 11 Jan 2007 13:21:57 -0600
> Michael Reed <[EMAIL PROTECTED]> wrote:
>
>> Testing on my ia64 system reveals
On Thu, 18 Jan 2007, Aubrey Li wrote:
> +int sysctl_pagecache_ratio = 10;
> +
Pagecache ratio is the ratio of memory to be left over? Would it not be
better to twist this around and to be able to specify how much of the
memory of a node may be used by the pagecache?
Why limit the size of the pa
On Fri, 2007-01-19 at 18:57 +0100, Peter Zijlstra wrote:
> On Fri, 2007-01-19 at 09:20 -0800, Christoph Lameter wrote:
> > On Fri, 19 Jan 2007, Peter Zijlstra wrote:
> >
> > > + /*
> > > + * NFS congestion size, scale with available memory.
> > > + *
> >
> > Well this all depends on the memory
On Fri, 19 Jan 2007, Trond Myklebust wrote:
> That would be good as a default, but I've been thinking that we could
> perhaps also add a sysctl in /proc/sys/fs/nfs in order to make it a
> tunable?
Good idea.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body o
On Fri, Jan 19, 2007 at 12:39:37PM -0500, Robert P. J. Day wrote:
> On Fri, 19 Jan 2007, Adrian Bunk wrote:
>
> > On Fri, Jan 19, 2007 at 11:56:30AM -0500, Robert P. J. Day wrote:
> > >
> > > Remove the macros that define simple "inlining" to mean forced
> > > inlining, since you can (and *shoul
On Thu, Jan 11, 2007 at 10:26:27PM -0800, Andrew Morton wrote:
>...
> Changes since 2.6.20-rc3-mm1:
>...
> git-ubi.patch
>...
> git trees
>...
This patch contains the following possible cleanups:
- make needlessly global code static
- remove the following unused variable:
- debug.c: alloc_pri
I have a very interesting question about something that we're seeing
happening with threading between Fedora Core 3 and Fedora Core 5. Running
on Dell PowerEdge 1800 Hardware with a Xeon processor with hyper-threading
turned on. Both systems are using a 2.6.16.16 kernel (MVP al la special).
We h
Aubrey Li wrote:
> On 1/19/07, Vaidyanathan Srinivasan <[EMAIL PROTECTED]> wrote:
>>
>> Hi Aubrey,
>>
>> The idea of creating separate flag for pagecache in page_alloc is
>> interesting. The good part is that you flag watermark low and the
>> zone reclaimer will do the rest of the job.
>>
>> How
Hi kernel developers
I don't know if this is the proper list but I have a very odd problem
and it's driving me nuts for the past two days.
I have a portable mp3 player named:
usb-storage: waiting for device to settle before scanning
Vendor: THOMSON Model: PDP95FM SeriesRev: 0100
Type:
On Fri, 2007-01-19 at 10:43 -0800, Brian McGrew wrote:
> I have a very interesting question about something that we're seeing
> happening with threading between Fedora Core 3 and Fedora Core 5. Running
> on Dell PowerEdge 1800 Hardware with a Xeon processor with hyper-threading
> turned on. Both
On 1/19/07 10:55 AM, "Arjan van de Ven" <[EMAIL PROTECTED]> wrote:
> On Fri, 2007-01-19 at 10:43 -0800, Brian McGrew wrote:
>> I have a very interesting question about something that we're seeing
>> happening with threading between Fedora Core 3 and Fedora Core 5. Running
>> on Dell PowerEdge 1800
On Sat, 20 Jan 2007, Vaidyanathan Srinivasan wrote:
> >> However when the zone reclaimer starts to reclaim pages, it will
> >> remove all cold pages and not specifically pagecache pages. This
> >> may affect performance of applications.
The reclaimer is passed a control structure that can be use
---
include/linux/cdev.h |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/include/linux/cdev.h b/include/linux/cdev.h
index f309b00..b53e2a0 100644
--- a/include/linux/cdev.h
+++ b/include/linux/cdev.h
@@ -5,6 +5,7 @@
#include
#include
#include
+#include
struct cd
On Tue, 9 Jan 2007 [EMAIL PROTECTED] wrote:
> Add a clockevent driver for pxa systems. This patch also removes the pxa
> dyntick support since it is not necessary anymore with generic dynamic
> tick support
>
> Signed-off-by: Luotao Fu <[EMAIL PROTECTED]>
> Signed-off-by: Sascha Hauer <[EMAIL PRO
On Fri, 19 Jan 2007 12:54:07 -0600 Noah Watkins wrote:
> ---
> include/linux/cdev.h |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/cdev.h b/include/linux/cdev.h
> index f309b00..b53e2a0 100644
> --- a/include/linux/cdev.h
> +++ b/include/linux/cdev.h
>
> And on FC5 I am using pthread_self but my problem isn't simply with
> pthread_self, it's with the scheduling.
maybe your kernel has a broken scheduler loadbalancing? you really
shouldn't have to do this manually. At all.
> On FC3 both threads run
> simultaneously in almost symmetric paral
--- Orion Poplawski <[EMAIL PROTECTED]> wrote:
> Robert Hancock wrote:
> > Orion Poplawski wrote:
> >> Can someone please explain to me what these mean?
> >>
> >> EDAC k8 MC1: general bus error: participating processor(local node
>
> >> origin), time-out(no timeout) memory transaction type(gener
On Fri, Jan 19, 2007 at 06:55:10PM +, Marco Ferra wrote:
> Hi kernel developers
>
> I don't know if this is the proper list but I have a very odd problem
> and it's driving me nuts for the past two days.
I suggest posting this to the linux-usb-devel mailing list, and
including your kernel ver
Greetings all;
I have a card reader plugged into a usb port. I recognizes a 512meg pny
cf card just fine, but wwhen I plug in a 256meg Lexar cf, the led comes
on, but there is no reaction from linux. /dev/sda is not created,
nothing.
Is this a kernel config problem, or is this particular cf k
On Fri, Jan 19, 2007 at 12:54:07PM -0600, Noah Watkins wrote:
> --- a/include/linux/cdev.h
> +++ b/include/linux/cdev.h
> @@ -5,6 +5,7 @@
> #include
> #include
> #include
> +#include
>
> struct cdev {
> struct kobject kobj;
It is not for "struct inode", but to a pointer to struct ino
Hello!
> Getting an error there is all the more reason to proceed
> with the swapoff, not to give up and break out of it.
Yes, from this viewpoint more reasonable approach would be to untie
corresponding ptes from swap entry and mark them as invalid to trigger
fault on access.
Not even tried sim
On Friday, 19. January 2007 16:05, Alistair John Strachan wrote:
> On Tuesday 16 January 2007 01:53, Jeff Garzik wrote:
> > Robert Hancock wrote:
> > > I'll try your stress test when I get a chance, but I doubt I'll run
> > > into the same problem and I haven't seen any similar reports. Perhaps
> >
On Fri, Jan 19, 2007 at 02:04:47PM +0200, Pekka Enberg wrote:
> On 1/18/07, Michael Halcrow <[EMAIL PROTECTED]> wrote:
> >+ page_data = (char *)kmap_atomic(page, KM_USER0);
> >+ lower_page_data = (char *)kmap_atomic(lower_page, KM_USER1);
>
> Drop 'em redundant casts, please.
Replace
On Wed, Dec 13, 2006 at 01:52:36PM +0100, Jens Axboe wrote:
> On Tue, Dec 12 2006, Mike Miller (OS Dev) wrote:
> > On Mon, Nov 06, 2006 at 09:32:00PM +0100, Jens Axboe wrote:
> > > On Mon, Nov 06 2006, Mike Miller (OS Dev) wrote:
> > > > PATCH 9 of 12
> > > >
> > > > This patch adds a check for bu
On Fri, Jan 19, 2007 at 11:57:00AM +0530, Suparna Bhattacharya ([EMAIL
PROTECTED]) wrote:
> > > Since you are implementing new APIs here, have you considered doing an
> > > aio_sendfilev to be able to send a header with the data ?
> >
> > It is doable, but why people do not like corking?
> > With
> Let me briefly describe your approach and possible drawbacks in it.
> You start reserving some memory when systems is under memory pressure.
> when system is in real trouble, you start using that reserve for special
> tasks mainly for network path to allocate packets and process them in
> order
On Thu, Jan 18, 2007 at 09:22:52PM +, Andrew Walrond wrote:
> Don't know exactly when this change went in, but it's not in 2.6.18.3
> and is in 2.6.19.2+
>
> $ diff linux/include/linux/if_arp.h linux-2.6/include/linux/if_arp.h
> 133,134c133,134
> < unsigned short ar_hrd; /* fo
On Thu, 18 Jan 2007, Peter Zijlstra wrote:
>
> > Cache misses for small packet flow due to the fact, that the same data
> > is allocated and freed and accessed on different CPUs will become an
> > issue soon, not right now, since two-four core CPUs are not yet to be
> > very popular and price fo
On Fri, 19 Jan 2007, Anssi Hannula wrote:
> The commit 4916b3a57fc94664677d439b911b8aaf86c7ec23 introduced a
> hid regression between 2.6.19 and 2.6.20-rc1. The device put in
> input_dev->cdev is now of type usb_device instead of usb_interface.
Yes, this is apparently a bug. Thanks a lot for the
1 - 100 of 170 matches
Mail list logo
