Le jeudi 10 mai 2007 à 16:01 -0700, Christoph Lameter a écrit :
> On Fri, 11 May 2007, Mel Gorman wrote:
>
> > Nicholas, could you backout the patch
> > dont-group-high-order-atomic-allocations.patch and test again please?
> > The following patch has the same effect. Thanks
>
> Great! Thanks.
[Andrew Morton - Thu, May 10, 2007 at 03:46:40PM -0700]
[...snip...]
| But please let's not add three copies of identical code. Do something like:
[...snip...]
Thanks for comments, Andrew. Let me rewrite the patch...
Cyrill
-
To unsubscribe from this list: send the line
On May 10, 2007, at 00:34:11, Kyle Moffett wrote:
On May 10, 2007, at 00:25:54, Ben Greear wrote:
Looks like a deadlock in the vlan code. Any chance you can run
this test with lockdep enabled?
You could also add a printk in vlan_device_event() to check which
event it is hanging on, and
which we want to skip during modpost processing. We need this to make
some of the whitelisting work.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
---
scripts/mod/modpost.c | 18 +-
1 files changed, 17 insertions(+), 1 deletions(-)
--
Cheers,
Stephen Rothwell
Jens Axboe wrote:
> On Thu, May 10 2007, Benny Halevy wrote:
>> Jens Axboe wrote:
>>> It's a subsystem function, prefix it as such.
>> Jens, Boaz and I talked about this over lunch.
>> I wonder whether the crypto code must use your implementation
>> instead of its own as it needs to over the
On Thu, 10 May 2007, William Lee Irwin III wrote:
> Looking more closely at it, the entire attempt to avoid struct page
> pointers is far beyond pointless. The freeing functions unconditionally
> require struct page pointers to either be passed or computed and the
> allocation function's virtual
Signed-off-by: Richard Knutsson <[EMAIL PROTECTED]>
---
Compile-tested with all(yes|mod|no)config on x86(|_64) & sparc(|64)
got some warnings on some builds, none related to this patch
Diffed against Linus' git-tree.
aic7xxx_old.c | 326
On Thu, May 10, 2007 at 12:59:18PM -0400, Mathieu Desnoyers wrote:
> * Alan Cox ([EMAIL PROTECTED]) wrote:
...
> > > * Third issue : Scalability. Changing code will stop every CPU on the
> > > system for a while. Compared to this, the int3-based approach will run
> > > through the breakpoint
Hi Remi,
On Thursday 10 May 2007 21:50, Andrew Morton wrote:
> On Thu, 10 May 2007 15:05:25 +0200
> Remi Colinet <[EMAIL PROTECTED]> wrote:
>
> > My D610 ALPS Glide Point is unresponsive with 2.6.21-mm1 patch.
> > No problem noticed with 2.6.21.
> >
> > The culprit seems to be git-input. I have
On Tue, May 08, 2007 at 10:15:21PM -0700, H. Peter Anvin wrote:
> Hello all,
>
> I believe the x86 setup tree is now finished. I will turn it into a
> "clean patchset" later this week, but I wanted to get flamed^W feedback
> on it first.
>
> The git tree is at:
>
>
[adding linux-scsi]
On Thu, 10 May 2007 23:59:10 -0400 Rob Landley wrote:
> Booting a 2.6.20 kernel under qemu works fine and gets me to a shell prompt,
> but booting a 2.6.21.1 kernel cycles endlessly on scsi, going:
>
> Loading iSCSI transport class v2.0-724.
> PCI: enabling device
On Thu, May 10, 2007 at 11:18:50PM +0100, Russell King wrote:
> On Fri, May 11, 2007 at 12:16:59AM +0200, Sam Ravnborg wrote:
> > On Thu, May 10, 2007 at 10:59:20PM +0100, Russell King wrote:
> > > file:(section+offset): message
> >
> > I like the new format - thanks!
> > Did you drop the ':'
Booting a 2.6.20 kernel under qemu works fine and gets me to a shell prompt,
but booting a 2.6.21.1 kernel cycles endlessly on scsi, going:
Loading iSCSI transport class v2.0-724.
PCI: enabling device :00:0c.0 (0140 -> 0143)
sym0: <895a> rev 0x0 at pci :00:0c.0 irq 0
sym0: No NVRAM, ID
Out of curiosity, since 2.2 hasn't had a release in 3 years, and the last
prepatch was 2 years ago, why is its' status still on the kernel.org main
page?
Not exactly something people are checking the status of on a daily basis...
Just wondering...
Rob
-
To unsubscribe from this list: send the
I have 2 kernel modules. In one module I have 2 global pointers(of type
unsigned char and int respectively). I'd like to use these 2 pointers in the
other module. I am adopting the following approach but not really sure whether
its right or not:
1. I have exported both the pointers using
On Wed, 09 May 2007 12:08:43 EDT, [EMAIL PROTECTED] said:
> On Wed, 09 May 2007 01:23:22 PDT, Andrew Morton said:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21/2.6.21-mm2/
>
> Boots up to multiuser mostly OK. However...
>
> It comes up with a screaming ksoftirqd -
On Thu, 10 May 2007, Len Brown wrote:
>
> That said, can you send me or point me to the acpidump output
> for your EVO. Yes, I'm sure you've sent it before a long time
> ago, but that was about probably 2,000,000 e-mail messages
> and a couple of disk crashes ago:-)
Sure. If you send me a
Tomohiro Kusumi wrote:
Dear Auke
> I'm ok with the bottom part of the patch, but I do not like
> the modification of the pci device ID table in this way. As
> Arjan van der Ven previously commented as well, this makes
> it hard for future device ID's to be bound to the driver.
I googled
On Fri, May 11, 2007 at 11:27:22AM +0900, Simon Horman wrote:
> On Thu, May 10, 2007 at 09:13:34PM -0500, Kumar Gala wrote:
> > On Fri, 11 May 2007, Simon Horman wrote:
> >
> > > On Thu, May 10, 2007 at 08:47:05PM -0500, Kumar Gala wrote:
> > > > Try this patch:
> > >
> > > That certainly
Enable the IR-remote of the 10moons TM300 card and add the key-codes for
it's remote.
It has been tested using lirc. All the key codes are accepted.
Signed-off-by: Tony Wan <[EMAIL PROTECTED]>
---
drivers/media/common/ir-keymaps.c | 69
+++
Dear Auke
> I'm ok with the bottom part of the patch, but I do not like
> the modification of the pci device ID table in this way. As
> Arjan van der Ven previously commented as well, this makes
> it hard for future device ID's to be bound to the driver.
I googled the previous comment by
Simon Horman wrote:
I agree. I had thought a little about a kconfig fix. Though I'm
wondering if removing the warning will lead to oodles of dangling
symbols and invalid checks over time.
I'm pretty sure it will. Perhaps we need to have a lint for Kconfig?
-
To unsubscribe from this list:
Paul Menage wrote:
> On 5/8/07, Balbir Singh <[EMAIL PROTECTED]> wrote:
>>
>> I now have a use case for maintaining a per-container task list.
>> I am trying to build a per-container stats similar to taskstats.
>> I intend to support container accounting of
>>
>> 1. Tasks running
>> 2. Tasks
On Thu, May 10, 2007 at 09:13:34PM -0500, Kumar Gala wrote:
> On Fri, 11 May 2007, Simon Horman wrote:
>
> > On Thu, May 10, 2007 at 08:47:05PM -0500, Kumar Gala wrote:
> > > Try this patch:
> >
> > That certainly resolves the problem for me.
> > I'll see about doing something like that for the
On Fri, May 11, 2007 at 08:35:27AM +0900, Paul Mundt wrote:
> On Thu, May 10, 2007 at 12:00:08PM -0700, Christoph Lameter wrote:
> > As far as I can tell there is only a single slab destructor left (there
> > is currently another in i386 but its going to go as soon as Andi merges
> > i386s
On Thursday May 10, [EMAIL PROTECTED] wrote:
> Ulrich Drepper wrote:
> > Neil Brown wrote:
> >> Does it also specify how to find out what granularity is used by the
> >> filesystem? I had a need for this just recently and couldn't see any
> >> way to extract it.
> >
> > That's still on the
On Fri, 11 May 2007, Simon Horman wrote:
> On Thu, May 10, 2007 at 08:47:05PM -0500, Kumar Gala wrote:
> > Try this patch:
>
> That certainly resolves the problem for me.
> I'll see about doing something like that for the similar
> Kconfig problems that I see.
>
> --
> Horms
> H:
The UCC_GETH Kconfig option in drivers/net/Kconfig had a line to select
the UCC_FAST option is arch/powerpc/sysdev/qe_lib/Kconfig, which is only used
on PowerPC builds. On other architectures, this would generated a warning.
The fix is to have UCC_FAST depend on UCC_GETH.
Signed-off-by: Timur
On Thu, May 10, 2007 at 08:47:05PM -0500, Kumar Gala wrote:
> Try this patch:
That certainly resolves the problem for me.
I'll see about doing something like that for the similar
Kconfig problems that I see.
--
Horms
H: http://www.vergenet.net/~horms/
W: http://www.valinux.co.jp/en/
-
To
Steven Rostedt wrote:
> Li Yu wrote:
>
>>> Now since mutexes can be defined by user-land applications, we don't
>>>
>> want a DOS
>>
>>> type of application that nests large amounts of mutexes to create a large
>>> PI chain, and have the code holding spin locks while looking at a
On May 10, 2007, at 8:25 PM, Simon Horman wrote:
On Thu, May 10, 2007 at 11:56:48AM -0500, Timur Tabi wrote:
Simon Horman wrote:
So my question is: in which Kconfig do I define "UCC_FAST_TEMP" and
"UCC_SLOW_TEMP"? At first I thought, just put it in drivers/
Kconfig, but
that Kconfig does
Bas Westerbaan wrote:
Hello,
Quite a lot of userspace applications cache. Firefox caches pages;
mySQL caches queries; libc' free (like practically all other
userspace allocators) won't directly return the first byte of memory
freed, etc.
These applications are unaware of memory pressure.
On Thu, 10 May 2007 15:05:25 +0200
Remi Colinet <[EMAIL PROTECTED]> wrote:
> My D610 ALPS Glide Point is unresponsive with 2.6.21-mm1 patch.
> No problem noticed with 2.6.21.
>
> The culprit seems to be git-input. I have applied 2.6.21-mm1 on top of 2.6.21
> and then removed git-input patch. It
On Fri, 11 May 2007, Simon Horman wrote:
> On Thu, May 10, 2007 at 11:56:48AM -0500, Timur Tabi wrote:
> > Simon Horman wrote:
> >
> > >>So my question is: in which Kconfig do I define "UCC_FAST_TEMP" and
> > >>"UCC_SLOW_TEMP"? At first I thought, just put it in drivers/Kconfig, but
> > >>that
On Thu, May 10, 2007 at 05:07:02PM -0700, William Lee Irwin III wrote:
> I described it as motivated by such, not really correctly handling it.
> I didn't bother analyzing it for correctness. I'm not surprised at all
> that the TLB flush can be missed where it now stands in the patch. I
> wanted
On Thu, May 10, 2007 at 11:56:48AM -0500, Timur Tabi wrote:
> Simon Horman wrote:
>
> >>So my question is: in which Kconfig do I define "UCC_FAST_TEMP" and
> >>"UCC_SLOW_TEMP"? At first I thought, just put it in drivers/Kconfig, but
> >>that Kconfig does nothing but including other Kconfigs.
Andrew Morton wrote:
On Thu, 10 May 2007 14:04:13 +0200
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
Hi all,
Here is a list of some known regressions in 2.6.21-gitX.
Feel free to add new regressions/remove fixed etc.
http://kernelnewbies.org/known_regressions
Networking:
Subject:
1) Use new lguest_send_dma & lguest_bind_dma functions.
2) sparse: lguest_cons can be static.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
---
drivers/char/hvc_lguest.c | 15 +--
1 file changed, 9 insertions(+), 6 deletions(-)
1) Use new dma wrapper functions, and handle bind failure (may happen
in future)
2) Use new lgdev_irq() "get me a good interrupt number" function.
3) __force the ioremap: guests can use it as normal memory.
Signed-off-by: Rusty Russell <[EMAIL PROTECTED]>
---
drivers/block/lguest_blk.c |
Feedback from Jeff Garzik:
1) Use netdev_priv instead of dev->priv.
2) Check for ioremap failure
3) iounmap on failure.
4) Wrap SEND_DMA and BIND_DMA calls
5) Don't set NETIF_F_SG unless we set NETIF_F_NO_CSUM
6) Use SET_NETDEV_DEV()
7) Don't set dev->irq, mem_start & mem_end (deprecated)
Sparse
On Thu, May 10, 2007 at 05:39:29PM +0200, Johannes Berg wrote:
> On Thu, 2007-05-10 at 14:10 +0900, Simon Horman wrote:
>
> > drivers/macintosh/Kconfig:112:warning: 'select' used by config symbol
> > 'PMAC_APM_EMU' refer to undefined symbol 'SYS_SUPPORTS_APM_EMULATION'
>
> Argh. Is that with
1) send-dma and bind-dma hypercall wrappers for drivers to use,
2) formalization of the convention that devices can use the irq
corresponding to their index on the lguest_bus.
3) ___force to shut up sparse: guests *can* use ioremap as virtual mem.
4) lguest.c should include "lguest_bus.h" for
1) Sam Ravnborg says lg-objs is deprecated, use lg-y.
2) Sparse: page_tables.c unnecessary initialization
3) Lots of __force to shut sparse up: guest "physical" addresses are
userspace virtual.
4) Change prototype of run_lguest and do cast in caller instead (when we add
__iomem to cast, it
Hi all,
Gratefully-received recent feedback from CC'd was applied to excellent
effect (and the advice from Matt Mackall about my personal appearance is
best unrequited).
The patch is split in 5 parts to correspond with the 9 parts Andrew
sent out before, but here's the summary:
On Thu, 10 May 2007 14:04:13 +0200
Michal Piotrowski <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Here is a list of some known regressions in 2.6.21-gitX.
>
> Feel free to add new regressions/remove fixed etc.
> http://kernelnewbies.org/known_regressions
>
>
>
> Unclassified:
>
> Subject:
On Thu, 10 May 2007 11:00:31 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 9 May 2007, Yasunori Goto wrote:
>
> >
> > +unsigned int nr_free_movable_pages(void)
> > +{
> > + unsigned long nr_pages = 0;
> > + struct zone *zone;
> > + int nid;
> > +
> > +
On 10 May 2007 15:44:08 +0200
Andi Kleen <[EMAIL PROTECTED]> wrote:
> Yasunori Goto <[EMAIL PROTECTED]> writes:
>
>
> (not a full review, just something I noticed)
> > @@ -352,6 +352,8 @@ struct sysinfo {
> > unsigned short pad; /* explicit padding for m68k */
> > unsigned
On Thu, May 10, 2007 at 05:07:02PM -0700, William Lee Irwin III wrote:
> quicklist_free() with unflushed TLB entries admits speculation through
> the pagetable entries corresponding to the list links. So tlb_finish_mmu()
> is the place to call quicklist_free() on pagetables. This requires
>
Christoph Hellwig wrote:
>
> I'd be happy to have them. While it's not the nicest API in the world
> it's in Posix and we have to support it at the library level, so we
> should better get it right.
>
> I'd like to avoid having a big swithc statement in every filesystem,
> though, instead of we
On Thu, 10 May 2007 11:09:29 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 9 May 2007, Yasunori Goto wrote:
>
> > +/*
> > + * Just an easy implementation.
> > + */
> > +static struct page *
> > +hotremove_migrate_alloc(struct page *page,
> > + unsigned long
On Thu, 10 May 2007 17:42:54 +0100 (IST)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> > + if (!pfn_valid(pfn))
> > + return -EINVAL;
>
> This may lead to boundary cases where pages cannot be captured at the
> start and end of non-aligned zones due to memory holes.
>
Hm, ok. maybe we can
Martin Mares wrote:
> Hello!
>
>> As far as I could tell, "scan" simply caused the nonstandard video
>> driver scan modules (unsafe probes) to be invoked. Since those modules
>> are no longer present, there appeared to be no need for them. The VGA
>> and VESA probes are safe.
>
> "scan" is
Hello,
Quite a lot of userspace applications cache. Firefox caches pages;
mySQL caches queries; libc' free (like practically all other
userspace allocators) won't directly return the first byte of memory
freed, etc.
These applications are unaware of memory pressure. While the kernel
is
On Thu, 10 May 2007 16:35:37 +0100 (IST)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> On Wed, 9 May 2007, Yasunori Goto wrote:
>
> > This patch add function drain_all_pages(void) to drain all
> > pages on per-cpu-freelist.
> > Page isolation will catch them in free_one_page.
> >
>
> Is this
Hi Rusty.
Following up the recent MODULE_MAINTAINER discussion:
http://lkml.org/lkml/2007/4/4/170
that concluded with MODULE_MAINTAINER not being a good idea, here's a small
patch that just deletes the advice of including an email address in the
MODULE_AUTHOR tag as suggested (and not
On Thu, 10 May 2007 11:07:08 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 9 May 2007, Yasunori Goto wrote:
>
> > This patch add function drain_all_pages(void) to drain all
> > pages on per-cpu-freelist.
> > Page isolation will catch them in free_one_page.
>
> This is only
On Thu, May 10, 2007 at 03:08:59PM +0200, Tejun Heo wrote:
> Paul Mundt wrote:
> > The detection is simply flaky after that point, however before the
> > current master it never hit the 35 second point (and thus never implied
> > that the link was down). I'll double check the bisect log to see if
> Scrollback rarely works as planned, for me. Overall, a balance must be
> found.
>
> More information is more helpful. But.
>
> There are downsides to spewing everything possible, upon error. You
> cause logging to the possibly problematic disk, you push older messages
> out of the printk
On Thu, 10 May 2007 11:04:37 -0700 (PDT)
Christoph Lameter <[EMAIL PROTECTED]> wrote:
> On Wed, 9 May 2007, Yasunori Goto wrote:
>
> > This patch is for supporting making page unused.
> >
> > Isolate pages by capturing freed pages before inserting free_area[],
> > buddy allocator.
> > If you
On Thu, 10 May 2007 16:34:01 +0100 (IST)
Mel Gorman <[EMAIL PROTECTED]> wrote:
> > +#ifdef CONFIG_PAGE_ISOLATION
> > + /*
> > +* For pages which are not used but not free.
> > +* See include/linux/page_isolation.h
> > +*/
> > + spinlock_t isolation_lock;
> > +
Satyam Sharma wrote:
> On 5/10/07, Xavier Bestel <[EMAIL PROTECTED]> wrote:
>> On Thu, 2007-05-10 at 16:51 +0200, Jan Engelhardt wrote:
>> > >(But Andrew never saw your email, I suspect: "[EMAIL PROTECTED]" is
>> > probably
>> > >some strange mixup of Andrew Morton and Andi Kleen in your mind ;)
On Thu, May 10, 2007 at 04:49:35PM -0700, Jeremy Fitzhardinge wrote:
> David Chinner wrote:
> > Ok, this is important to kow becase we merged a mod around that time
> > that changes the way we handle the updates to the file size i.e. the
> > fix for the NULL-files-on-crash problem:
> >
> >
On Thu, May 10, 2007 at 04:01:52AM -0700, David Miller wrote:
>
> It's not OK, please use the generic netlink interface and as
> such you will not need to allocate any numbers at all.
>
> Documentation/networking/generic_netlink.txt gives a link
> to some infomration on this topic.
Where can I
Upcoming 1.5.2 will have three large-ish new features that the
user community wished to have for quite some time. I usually do
not CC the kernel list for -rc releases, but this one will
hopefully be pretty much the same as what the final one would
look like, so here it is.
We may get around
On Thu, 10 May 2007, William Lee Irwin III wrote:
>> So now quicklist semantics vs. TLB flushing are the motive behind the
>> odd flush_tlb_mm() affair. The real trick with it is that flushing
>> must never occur until the TLB flush. Any change to the core quicklist
>> code that retires pages back
David Chinner wrote:
> Ok, this is important to kow becase we merged a mod around that time
> that changes the way we handle the updates to the file size i.e. the
> fix for the NULL-files-on-crash problem:
>
>
Robert Hancock wrote:
>Gerhard Mack wrote:
>> On Wed, 9 May 2007, Jeff Garzik wrote:
>>> Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct
0x0 SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
On Thu, 10 May 2007 10:22:23 -0700
Daniel Walker <[EMAIL PROTECTED]> wrote:
> Switch to the defines for these two checks, instead of hard
> coding the values.
>
> Signed-Off-By: Daniel Walker <[EMAIL PROTECTED]>
>
> ---
> kernel/sys.c |4 ++--
> 1 file changed, 2 insertions(+), 2
Robert Hancock wrote:
I don't think this is as big of a deal here as in other cases, like oops
output. With libata errors, if they're at the console (which they'd have
to be to see these messages), unless something has actually caused a
panic the scrollback buffer should still be functional
On Thu, 10 May 2007 08:48:02 -0700 Randy Dunlap <[EMAIL PROTECTED]> wrote:
>
> On Thu, 10 May 2007 22:16:31 +1000 Stephen Rothwell wrote:
>
> > On Thu, 10 May 2007 12:48:28 +0100 Andy Whitcroft <[EMAIL PROTECTED]> wrote:
> > >
> > > arch/powerpc/platforms/pseries/power.c:31: warning: `struct
On Thu, 10 May 2007 19:10:42 +0200
Tomas Janousek <[EMAIL PROTECTED]> wrote:
> Commit 411187fb05cd11676b0979d9fbf3291db69dbce2 caused boot time to move and
> process start times to become invalid after suspend. Using boot based time for
> those restores the old behaviour and fixes the issue.
>
>
On Thu, 10 May 2007 19:10:25 +0200
Tomas Janousek <[EMAIL PROTECTED]> wrote:
> The commits
> 411187fb05cd11676b0979d9fbf3291db69dbce2 (GTOD: persistent clock support)
> c1d370e167d66b10bca3b602d3740405469383de (i386: use GTOD persistent clock
> support)
> changed the monotonic time so
On Thu, May 10, 2007 at 12:00:08PM -0700, Christoph Lameter wrote:
> As far as I can tell there is only a single slab destructor left (there
> is currently another in i386 but its going to go as soon as Andi merges
> i386s support for quicklists).
>
> I wonder how difficult it would be to
William Lee Irwin III wrote:
>> Xen is not mandatory as it now stands.
On Thu, May 10, 2007 at 02:28:05PM -0700, Jeremy Fitzhardinge wrote:
> ? I'm hoping to merge the Xen code in the next couple of days, so I'd
> appreciate it if we don't break the foundations just before building the
>
Jeff Garzik wrote:
Mark Lord wrote:
If we're compiling the messages into the kernel regardless,
then it doesn't really make much sense to NOT show all of them
on the error paths.
Not true. Uncontrolled message spewage inevitably results in critical
information scrolling off the screen,
On Thu, 2007-05-10 at 18:38 -0400, J. Bruce Fields wrote:
> In 9d6a8c5c213e34c475e72b245a8eb709258e968c we changed posix_test_lock
> to modify its single file_lock argument instead of taking separate input
> and output arguments. This makes it no longer safe to set the output
> lock's fl_type to
Tejun Heo wrote:
+if (ehc->i.serror)
+ata_port_printk(ap, KERN_ERR,
+ "SError: {%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s%s}\n",
+ ehc->i.serror & SERR_DATA_RECOVERED ? "RecovDataErr " : "",
+ ehc->i.serror & SERR_COMM_RECOVERED ? "RecovCommErr " : "",
+
On Thu, May 10, 2007 at 04:07:30PM -0700, Jeremy Fitzhardinge wrote:
> David Chinner wrote:
> > Just to confirm this isn't a result of a recent change, can you reproduce
> > this on a 2.6.20 or 2.6.21 kernel? (sorry if you've already done this -
> > I've juggling
> > some many things at once it's
On Thu, 10 May 2007 15:33:34 +0100
David Howells <[EMAIL PROTECTED]> wrote:
> Following bug was uncovered by compiling with '-W' flag:
gcc -W finds a number of fairly scary bugs.
More than one would expect, given that it is recommended in
Documentation/SubmitChecklist, which everyone reads ;)
-
On Thu, 10 May 2007, William Lee Irwin III wrote:
> On Thu, May 10, 2007 at 09:03:39PM +0100, Hugh Dickins wrote:
> > Though when I look at the patchset (copied below), I do wonder why
> > it puts a quicklist_trim() into i386's cpu_idle() and flush_tlb_mm():
> > neither is where I'd expect us to
Andi Kleen wrote:
Probably. In principle getcpu() (where does the sched_ come from btw?)
getcpu() is an unacceptable name. All te other functions dealing with
CPU (sets, etc) have a sched_ prefix.
is only designed for the case where you don't set the affinity explicitely;
otherwise you
On Thu, May 10, 2007 at 05:51:29PM -0400, Chuck Ebbert wrote:
> Jeremy Fitzhardinge wrote:
> > Chuck Ebbert wrote:
> >> What CPU architecture is this happening on? Not i686 with PAE by
> >> any chance?
> >
> > Yes. Why?
>
> I have a bug report where NFS files are corrupted only with PAE
David Chinner wrote:
> Just to confirm this isn't a result of a recent change, can you reproduce
> this on a 2.6.20 or 2.6.21 kernel? (sorry if you've already done this - I've
> juggling
> some many things at once it's easy to forget little things).
It is the result of a recent change. I had
On Thu, 10 May 2007 14:06:54 +0800
"Zhang, Yanmin" <[EMAIL PROTECTED]> wrote:
> On Sun, 2007-05-06 at 16:00 +0100, Richard Kennedy wrote:
> > On Fri, 2007-05-04 at 23:32 +0900, Komuro wrote:
> > > On Thu, 03 May 2007 15:29:19 +0100
> > > Richard Kennedy <[EMAIL PROTECTED]> wrote:
> > >
> > >
>
On (10/05/07 15:49), Christoph Lameter didst pronounce:
> On Thu, 10 May 2007, Mel Gorman wrote:
>
> > > I cannot predict how allocations on a slab will be performed. In order
> > > to avoid the higher order allocations in we would have to add a flag
> > > that tells SLUB at slab creation
On Fri, 11 May 2007, Mel Gorman wrote:
> Nicholas, could you backout the patch
> dont-group-high-order-atomic-allocations.patch and test again please?
> The following patch has the same effect. Thanks
Great! Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the
On Thu, May 10, 2007 at 02:54:25PM -0700, Jeremy Fitzhardinge wrote:
> Chuck Ebbert wrote:
> > Jeremy Fitzhardinge wrote:
> >
> >> Chuck Ebbert wrote:
> >>
> >>> What CPU architecture is this happening on? Not i686 with PAE by
> >>> any chance?
> >>>
> >> Yes. Why?
> >>
> >
>
On Thursday 10 May 2007 16:56, Linus Torvalds wrote:
>
> On Thu, 10 May 2007, Linus Torvalds wrote:
> >
> > Seems to work for me. My evo correctly started the fan, and stopped it
> > when the temperature went down again.
>
> Looking at things in "top", I do end up occasionally seeing spikes
* Jeremy Fitzhardinge ([EMAIL PROTECTED]) wrote:
> Yep, this patch gets rid of my spinning thread. I can't find this patch
> or any discussion on marc.info; is there a better netdev list archive?
See the "linkwatch bustage in git-net" thread on netdev
From: Jeremy Fitzhardinge <[EMAIL PROTECTED]>
Date: Thu, 10 May 2007 15:45:42 -0700
> David Miller wrote:
> > I'm not so certain now that we know it's the jiffies wrap point :-)
> >
> > The fixes in question are attached below and they were posted and
> > discussed on netdev:
> >
>
> Yep,
On Thu, 10 May 2007, Mel Gorman wrote:
> > I cannot predict how allocations on a slab will be performed. In order
> > to avoid the higher order allocations in we would have to add a flag
> > that tells SLUB at slab creation creation time that this cache will be
> > used for atomic allocs and
Alexander van Heukelum wrote:
> On Thu, May 10, 2007 at 11:08:10AM -0700, H. Peter Anvin wrote:
>> As far as I could tell, "scan" simply caused the nonstandard video
>> driver scan modules (unsafe probes) to be invoked. Since those modules
>> are no longer present, there appeared to be no need
On Thu, May 10, 2007 at 03:24:58PM -0700, Ulrich Drepper wrote:
> The attached test program fails on a dual core (and probably SMP)
> machine on x86-64. Depending on where the thread starts, in one of the
> iterations the sched_setffinity() call succeeds but then sched_getcpu()
> fails to
On Thu, 10 May 2007 18:00:00 +0400
Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
> This patch adds cheking for granted memory while
> filling up inode data to prevent possible NULL
> pointer usage. If there is not enough memory to
> fill inode data we just mark it as "bad".
>
> Signed-off-by:
David Miller wrote:
> I'm not so certain now that we know it's the jiffies wrap point :-)
>
> The fixes in question are attached below and they were posted and
> discussed on netdev:
>
Yep, this patch gets rid of my spinning thread. I can't find this patch
or any discussion on marc.info; is
On (10/05/07 15:27), Christoph Lameter didst pronounce:
> On Thu, 10 May 2007, Mel Gorman wrote:
>
> > On (10/05/07 15:11), Christoph Lameter didst pronounce:
> > > On Thu, 10 May 2007, Mel Gorman wrote:
> > >
> > > > I see the gfpmask was 0x84020. That doesn't look like __GFP_WAIT was
> > > >
On Thu, May 10, 2007 at 05:26:20PM +0530, Amit K. Arora wrote:
> On Thu, May 10, 2007 at 10:59:26AM +1000, David Chinner wrote:
> > On Wed, May 09, 2007 at 09:31:02PM +0530, Amit K. Arora wrote:
> > > I have the updated patches ready which take care of Andrew's comments.
> > > Will run some tests
On Tue, 10 Apr 2007 21:17:40 +0200 (MEST)
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> the following patch series turns some menus into menuconfigs, so they
> can be disabled whilst "walking" thorugh the parent menu (check the
> videos [1], [2] to see what I mean), enabling for disabling lots of
In 9d6a8c5c213e34c475e72b245a8eb709258e968c we changed posix_test_lock
to modify its single file_lock argument instead of taking separate input
and output arguments. This makes it no longer safe to set the output
lock's fl_type to F_UNLCK before looking for a conflict, since that
means searching
On (10/05/07 14:49), Christoph Lameter didst pronounce:
> On Thu, 10 May 2007, Andrew Morton wrote:
>
> > Christoph, can we please take a look at /proc/slabinfo and its slub
> > equivalent (I forget what that is?) and review any and all changes to the
> > underlying allocation size for each
1 - 100 of 1284 matches
Mail list logo
