All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hans-Peter Jansen" <hpj@urpla.net>
To: Dave Chinner <david@fromorbit.com>
Cc: opensuse-kernel@opensuse.org, linux-kernel@vger.kernel.org,
	xfs@oss.sgi.com
Subject: Re: 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098]
Date: Tue, 13 Apr 2010 11:42:33 +0200	[thread overview]
Message-ID: <201004131142.33518.hpj@urpla.net> (raw)
In-Reply-To: <20100413091823.GD7544@dastard>

On Tuesday 13 April 2010, 11:18:23 Dave Chinner wrote:
> On Tue, Apr 13, 2010 at 10:50:35AM +0200, Hans-Peter Jansen wrote:
> >
> > Dave, may I ask you kindly for briefly elaborating on the worst
> > consequences of just reverting this hunk, as I've done before?
>
> Well, given that is the new shrinker code generating the warnings,
> reverting/removing that hunk will render the patch useless :0

Excuse me, I didn't express myself well. I'm after the consequences of 
applying the revert, that I posted a few messages above. 

> I'll get you a working 2.6.33 patch tomorrow - it's dinner time
> now....

Cool, thanks. 

Have a nice dinner,
Pete



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: "Hans-Peter Jansen" <hpj@urpla.net>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-kernel@vger.kernel.org, opensuse-kernel@opensuse.org,
	xfs@oss.sgi.com
Subject: Re: 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098]
Date: Tue, 13 Apr 2010 11:42:33 +0200	[thread overview]
Message-ID: <201004131142.33518.hpj@urpla.net> (raw)
In-Reply-To: <20100413091823.GD7544@dastard>

On Tuesday 13 April 2010, 11:18:23 Dave Chinner wrote:
> On Tue, Apr 13, 2010 at 10:50:35AM +0200, Hans-Peter Jansen wrote:
> >
> > Dave, may I ask you kindly for briefly elaborating on the worst
> > consequences of just reverting this hunk, as I've done before?
>
> Well, given that is the new shrinker code generating the warnings,
> reverting/removing that hunk will render the patch useless :0

Excuse me, I didn't express myself well. I'm after the consequences of 
applying the revert, that I posted a few messages above. 

> I'll get you a working 2.6.33 patch tomorrow - it's dinner time
> now....

Cool, thanks. 

Have a nice dinner,
Pete




  reply	other threads:[~2010-04-13  9:40 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-04 22:49 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer Hans-Peter Jansen
2010-04-04 22:49 ` Hans-Peter Jansen
2010-04-05  0:49 ` Dave Chinner
2010-04-05  0:49   ` Dave Chinner
2010-04-05 11:35   ` Hans-Peter Jansen
2010-04-05 11:35     ` Hans-Peter Jansen
2010-04-05 23:06     ` Dave Chinner
2010-04-05 23:06       ` Dave Chinner
2010-04-06 14:52       ` 2.6.34-rc3: simple du (on a big xfs tree) triggers oom killer [bisected: 57817c68229984818fea9e614d6f95249c3fb098] Hans-Peter Jansen
2010-04-06 14:52         ` Hans-Peter Jansen
2010-04-06 23:11         ` Dave Chinner
2010-04-06 23:11           ` Dave Chinner
2010-04-07  1:45           ` Dave Chinner
2010-04-07  1:45             ` Dave Chinner
2010-04-07 22:02             ` Hans-Peter Jansen
2010-04-07 22:02               ` Hans-Peter Jansen
2010-04-12 22:32               ` Dave Chinner
2010-04-12 22:32                 ` Dave Chinner
2010-04-13  8:50                 ` Hans-Peter Jansen
2010-04-13  8:50                   ` Hans-Peter Jansen
2010-04-13  9:18                   ` Dave Chinner
2010-04-13  9:18                     ` Dave Chinner
2010-04-13  9:42                     ` Hans-Peter Jansen [this message]
2010-04-13  9:42                       ` Hans-Peter Jansen
2010-04-24 16:44                       ` Hans-Peter Jansen
2010-04-24 16:44                         ` Hans-Peter Jansen
2010-04-24 21:23                         ` Emmanuel Florac
2010-04-24 21:23                           ` Emmanuel Florac
2010-04-24 22:30                           ` Hans-Peter Jansen
2010-04-24 22:30                             ` Hans-Peter Jansen
2010-04-24 22:40                             ` [opensuse-kernel] " Justin P. Mattock
2010-04-24 22:40                               ` Justin P. Mattock
2010-04-24 22:41                             ` Justin P. Mattock
2010-04-24 22:41                               ` Justin P. Mattock
2010-04-25 13:04                             ` Emmanuel Florac
2010-04-25 13:04                               ` Emmanuel Florac
2010-04-25 16:27                         ` Greg KH
2010-04-25 16:27                           ` Greg KH
2010-04-25 16:57                           ` Christoph Hellwig
2010-04-25 16:57                             ` Christoph Hellwig
2010-04-25 18:18                             ` Greg KH
2010-04-25 18:18                               ` Greg KH
2010-04-26  0:36                           ` Dave Chinner
2010-04-26  0:36                             ` Dave Chinner
2010-04-27  0:02                             ` Greg KH
2010-04-27  0:02                               ` Greg KH
2010-04-26  0:32                         ` Dave Chinner
2010-04-26  0:32                           ` Dave Chinner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201004131142.33518.hpj@urpla.net \
    --to=hpj@urpla.net \
    --cc=david@fromorbit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opensuse-kernel@opensuse.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.