[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] maint: cleanup size determination in sort [was: overly aggre
From: |
Jim Meyering |
Subject: |
Re: [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c] |
Date: |
Wed, 20 Jun 2012 14:45:05 +0200 |
Jeff Janes wrote:
> On Wed, Jun 20, 2012 at 12:16 AM, Jim Meyering <address@hidden> wrote:
>> Bernhard Voelker wrote:
>>> Here's a patch to move the code regarding physical/available/total
>>> memory down to where it's used (on top of your patch).
>>
>> Thanks. I've pushed that -- tweaked to move the rlimit declaration down,
>> too:
>
> The committed version does not include the limit to no more than 75%
> of physical memory. Was that intentional or an oversight?
Bernhard's patch was quite deliberately (as the commit log says)
intended to induce no semantic change.
- overly aggressive memory usage by sort.c, Jeff Janes, 2012/06/07
- Re: overly aggressive memory usage by sort.c, Pádraig Brady, 2012/06/07
- Re: overly aggressive memory usage by sort.c, Jim Meyering, 2012/06/11
- Re: overly aggressive memory usage by sort.c, Paul Eggert, 2012/06/11
- Re: overly aggressive memory usage by sort.c, Paul Eggert, 2012/06/11
- RE: overly aggressive memory usage by sort.c, Voelker, Bernhard, 2012/06/11
- Re: overly aggressive memory usage by sort.c, Paul Eggert, 2012/06/11
- [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c], Bernhard Voelker, 2012/06/14
- Re: [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c], Jim Meyering, 2012/06/20
- Re: [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c], Jeff Janes, 2012/06/20
- Re: [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c],
Jim Meyering <=
- Re: [PATCH] maint: cleanup size determination in sort [was: overly aggressive memory usage by sort.c], Paul Eggert, 2012/06/20
- Re: overly aggressive memory usage by sort.c, Jeff Janes, 2012/06/12