From: Karel Zak <kzak@redhat.com>
To: chenditang <chendt.fnst@cn.fujitsu.com>
Cc: util-linux@vger.kernel.org, linux-nfs@vger.kernel.org,
Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [QUESTION]about libmount library performance problems
Date: Tue, 25 Sep 2012 12:31:42 +0200 [thread overview]
Message-ID: <20120925103142.GC22639@x2.net.home> (raw)
In-Reply-To: <20120925101031.GB22639@x2.net.home>
On Tue, Sep 25, 2012 at 12:10:31PM +0200, Karel Zak wrote:
> On Tue, Sep 25, 2012 at 10:02:35AM +0800, chenditang wrote:
> > Question)*:* merg the tow file are necessary for umount a dir?
Ah, do you mean -- why we need to merge all the entries when we want
to work with only one mountpoint? That's good question ;-) I'll try
to improve the code...
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2012-09-25 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <505FBE77.8030802@cn.fujitsu.com>
[not found] ` <5061076C.2080707@cn.fujitsu.com>
2012-09-25 2:02 ` [QUESTION]about libmount library performance problems chenditang
2012-09-25 10:10 ` Karel Zak
2012-09-25 10:31 ` Karel Zak [this message]
2012-09-25 14:58 ` Karel Zak
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=20120925103142.GC22639@x2.net.home \
--to=kzak@redhat.com \
--cc=chendt.fnst@cn.fujitsu.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=util-linux@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).