mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@nl.linux.org>
To: lk@tantalophile.demon.co.uk, phillips@nl.linux.org
Cc: acahalan@cs.uml.edu, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Ext2 Directory Index - File Structure
Date: Sun, 15 Apr 2001 18:23:18 +0200	[thread overview]
Message-ID: <20010415162320Z92253-21911+19@humbolt.nl.linux.org> (raw)

>Daniel Phillips wrote:
> > Jamie Lokier wrote:
> > > Daniel Phillips wrote:
> > > > ls already can't handle the directories I'm working with on a regular
> > > > basis.  It's broken and needs to be fixed.  A merge sort using log n
> > > > temporary files is not hard to write.
> > >
> > > ls -U | sort
> > >
> > > should do the trick.
> >
> > Um, yep.  Now ls should do that itself instead of giving up with an error.
>
> Sorting 1 million 30-character strings does not require temporary files
> on a machine with > 35 MB anyway, and that can be virtual, so if anyone
> cares about ls sorting huge directories I suggest improving the
> in-memory sort.

I got this today:

	ls -U <big directory> 
	ls: Memory exhausted

Since this occured while nothing else was active, it's probably a MM bug
and I will chase it further.  However, it also shows that ls is well and
truly borked.  If anybody is going to work on it I'd suggest not only
improving the in-memory sort but adding a custom file-based sort or exec
sort as a fallback.
--
Daniel

             reply	other threads:[~2001-04-15 16:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-15 16:23 Daniel Phillips [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-04-13 20:55 Daniel Phillips
2001-04-13 22:40 ` Jamie Lokier
2001-04-11 13:07 Daniel Phillips
2001-04-11 16:08 ` Jamie Lokier
2001-04-11 13:00 Daniel Phillips
2001-04-09 10:40 Daniel Phillips
2001-04-09 18:35 ` Andreas Dilger
2001-04-10  9:36 ` Albert D. Cahalan

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=20010415162320Z92253-21911+19@humbolt.nl.linux.org \
    --to=phillips@nl.linux.org \
    --cc=acahalan@cs.uml.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lk@tantalophile.demon.co.uk \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®