All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Labute <dan@discreet.com>
To: reiserfs-list@namesys.com
Subject: Creating large numbers of files
Date: Mon, 10 Jan 2005 17:34:21 -0500	[thread overview]
Message-ID: <41E302ED.9040606@discreet.com> (raw)
In-Reply-To: <1105395827.2871.ezmlm@namesys.com>

Hi all,

I'm a developer trying to create large numbers of *empty* files 
(~100000).  What is the fastest way to perform such an operation other 
than a simple open().  Will using multiple threads to perform concurrent 
operations help significantly, or am I just awell-off using a single thread?

Are there any extensions that could be used?  What about writing my own 
filesystem plugin?

Similarly, I'd like to create and destroy large numbers of hard & soft 
links.  What are my options?

(Apologies if these questions have been asked in other thread.)

Thanks,

Dan


       reply	other threads:[~2005-01-10 22:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1105395827.2871.ezmlm@namesys.com>
2005-01-10 22:34 ` Dan Labute [this message]
2005-01-10 23:18   ` Creating large numbers of files Andreas Dilger
2005-01-11 21:34     ` Dan Labute

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=41E302ED.9040606@discreet.com \
    --to=dan@discreet.com \
    --cc=reiserfs-list@namesys.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.