From: "Toralf Förster" <toralf.foerster@gmx.de>
To: bo.li.liu@oracle.com
Cc: linux-btrfs@vger.kernel.org
Subject: Re: v3.18-rc2 at a 32 bit KVM gives :"INFO: trying to register non-static key.the code is fine but needs lockdep annotation."
Date: Fri, 31 Oct 2014 15:42:43 +0100 [thread overview]
Message-ID: <54539FE3.6010006@gmx.de> (raw)
In-Reply-To: <20141031141252.GA7522@localhost.localdomain>
On 10/31/2014 03:12 PM, Liu Bo wrote:
> Can you please tell me the trinity option?
>
> (I'm using "trinity --dangerous -C 2 -N 200 -c writev -q -l off", But I only got softlockup for one time, others are OOM messages.)
>
> thanks,
> -liubo
I'm running within the 32 bit KVM guest :
$> mkdir /mnt/ramdisk/btrfs; truncate -s 97M /mnt/ramdisk/btrfs.fs; /sbin/mkfs.btrfs /mnt/ramdisk/btrfs.fs; sudo su -c "mount -o loop,compress=lzo /mnt/ramdisk/btrfs.fs /mnt/ramdisk/btrfs; chmod 777 /mnt/ramdisk/btrfs"
followed by :
$> D=': D=/mnt/ramdisk/btrfs; while [[ : ]]; do cd ~; sudo rm -rf $D/t3 && mkdir $D/t3 || break; cd $D/t3; mkdir -p v1/v2; for i in $(seq 0 99); do touch v1/v2/f$i; mkdir v1/v2/d$i; done; trinity -C 2 -N 100000 -V $D/t3/v1/v2 -q; echo; echo " done"; echo; sleep 4; done
(latest git tree of trinity and Btrfs v3.14.2
--
Toralf
pgp key: 0076 E94E
prev parent reply other threads:[~2014-10-31 14:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 16:56 v3.18-rc2 at a 32 bit KVM gives :"INFO: trying to register non-static key.the code is fine but needs lockdep annotation." Toralf Förster
2014-10-30 10:15 ` Liu Bo
2014-10-30 23:33 ` Toralf Förster
2014-10-31 1:36 ` Liu Bo
2014-10-31 10:36 ` Toralf Förster
2014-10-31 14:12 ` Liu Bo
2014-10-31 14:42 ` Toralf Förster [this message]
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=54539FE3.6010006@gmx.de \
--to=toralf.foerster@gmx.de \
--cc=bo.li.liu@oracle.com \
--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