From: lakshmipathi.g@giis.co.in
To: dsterba@suse.cz, "Lakshmipathi.G" <Lakshmipathi.G@giis.co.in>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH]btrfs-progs: Add fast,slow symlinks and fifo types to convert test
Date: Tue, 20 Sep 2016 10:03:11 -0600 [thread overview]
Message-ID: <d094623632a3d60468d6ac0cb93ac48b@giis.co.in> (raw)
In-Reply-To: <20160919170503.GL16983@twin.jikos.cz>
On 2016-09-19 11:05, David Sterba wrote:
> On Thu, Sep 15, 2016 at 11:34:07AM +0200, Lakshmipathi.G wrote:
>> + slow_symlink)
>> + for num in $(seq 1 $DATASET_SIZE); do
>> + fname64=`date +%s | sha256sum | cut -f1 -d'-'`
>
> Do you need to generate the date and sha all the time?
>
Right, I missed that part. We can create a single file and create
multiple symlink to that same file. fname64 creation can be moved out of
the loop. I'll re-send another patch with this fix.
Cheers.
Lakshmipathi.G
next prev parent reply other threads:[~2016-09-20 16:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-15 9:34 [PATCH]btrfs-progs: Add fast,slow symlinks and fifo types to convert test Lakshmipathi.G
2016-09-19 17:05 ` David Sterba
2016-09-20 16:03 ` lakshmipathi.g [this message]
[not found] ` <89977db3-aae4-01d1-62a2-34011e0227f8@cn.fujitsu.com>
2016-09-20 16:06 ` lakshmipathi.g
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=d094623632a3d60468d6ac0cb93ac48b@giis.co.in \
--to=lakshmipathi.g@giis.co.in \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@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).