From: Paulo Marques <pmarques@grupopie.com>
To: sankarshana rao <san_wipro@yahoo.com>
Cc: root@chaos.analogic.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Inode question
Date: Thu, 22 Jul 2004 15:23:30 +0100 [thread overview]
Message-ID: <1090506209.8842.20.camel@pmarqueslinux> (raw)
In-Reply-To: <20040721225752.90581.qmail@web50902.mail.yahoo.com>
On Wed, 2004-07-21 at 23:57, sankarshana rao wrote:
> Guys,
> Thx for the inputs...I got it with path_lookup....
>
> Can I pass the inode pointer back to the user space???
To get an inode number from user space you can simply use the "stat" or
"fstat" functions. You don't need to create your own module.
> I have a scenario in which I have to create multiple
> folders on the harddisk. The number of folders can be
> in hundreds. Instead of parsing the path name
> everytime I need to create a folder (that's what
> sys_mkdir does??? ), I was thinking if I have the
> inode* of the parent folder, I can avoid this parsing
> and directly create a subfolder under the parent
> folder...
Is this really a problem? The dentry cache should make this quite fast,
leaving the bottleneck to the actual write on disk of the result.
I tried a small program (if it can be called a program) to create a
thousand directories and it takes less than 100 ms on my machine.
Best regards,
--
Paulo Marques - www.grupopie.com
"In a world without walls and fences who needs windows and gates?"
next prev parent reply other threads:[~2004-07-22 14:23 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 18:39 Inode question sankarshana rao
2004-07-21 20:25 ` Dave Kleikamp
2004-07-21 20:46 ` sankarshana rao
2004-07-21 20:56 ` Dave Kleikamp
2004-07-21 21:09 ` Richard B. Johnson
2004-07-21 22:57 ` sankarshana rao
2004-07-22 12:36 ` Dave Kleikamp
2004-07-22 14:23 ` Paulo Marques [this message]
2004-07-27 1:28 ` sankarshana rao
2004-07-27 11:18 ` Paulo Marques
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=1090506209.8842.20.camel@pmarqueslinux \
--to=pmarques@grupopie.com \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
--cc=san_wipro@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox