mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Walker <danielwa@cisco.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "Nikunj Kela (nkela)" <nkela@cisco.com>,
	Richard Weinberger <richard.weinberger@gmail.com>,
	"linux-mtd @ lists . infradead . org"
	<linux-mtd@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"xe-linux-external(mailer list)" <xe-linux-external@cisco.com>
Subject: Re: [PATCH] jffs2: implement mount option to configure endianness
Date: Mon, 12 Nov 2018 13:43:33 -0800	[thread overview]
Message-ID: <20181112214333.lplffcc722hta43v@zorba> (raw)
In-Reply-To: <897867ec09af82ca76c642b48ad23a7f08838dcf.camel@infradead.org>

On Thu, Nov 08, 2018 at 07:47:08PM +0000, David Woodhouse wrote:
> On Thu, 2018-11-08 at 18:01 +0000, Nikunj Kela (nkela) wrote:
> >     But we can hypothesise and handwave about it until the cows come home;
> >     I'd like to see a real test of whether it actually makes a difference
> >     that we care about.
> >     
> >     If it does, one option might be to just build separate versions of
> >     scan.c for each endianness, since that's the critical path we care
> >     about.
> > 
> > I wonder if this feature is really that important that we need to duplicate the drivers.
> > Also, it might take some time for me to find some device that I can run the tests with and without this patch.
> 
> Hm?
> 
> # modprobe mtdram size=16384
> # mount -tjffs2 mtd0 /mnt
> # cp -av .git /mnt # until it fills up
> # umount /mnt
> # perf record mount -tjffs2 mtd0 /mnt
> 
> On my desktop 'perf' only gets about 12 samples from that, so it's not
> ideal. But you can make the mtdram device bigger, use something other
> than my shiny new laptop, and use a higher sample frequency from 'perf'
> and you should be able to get some vaguely meaningful results.
> 

10 meg MTDRAM device baseline without any changes,

sh-4.2# perf stat -B  mount -tjffs2 /dev/mtdblock7 /mnt
jffs2: Flash size not aligned to erasesize, reducing to 9920KiB

 Performance counter stats for 'mount -tjffs2 /dev/mtdblock7 /mnt':

         74.922624 task-clock                #    0.820 CPUs utilized          
                14 context-switches          #    0.187 K/sec                  
                 0 cpu-migrations            #    0.000 K/sec                  
                94 page-faults               #    0.001 M/sec                  
         103274114 cycles                    #    1.378 GHz                     [ 6.65%]
           1887555 stalled-cycles-frontend   #    1.83% frontend cycles idle   
           1688520 stalled-cycles-backend    #    1.63% backend  cycles idle   
         106423876 instructions              #    1.03  insns per cycle        
                                             #    0.02  stalled cycles per insn
          21325416 branches                  #  284.633 M/sec                   [97.41%]
            104797 branch-misses             #    0.49% of all branches         [95.20%]

       0.091398368 seconds time elapsed


Same partition size, adding in the patch from Nikunj set to Native,

sh-4.2# perf stat -B mount -t jffs2 /dev/mtdblock7 /mnt
jffs2: Flash size not aligned to erasesize, reducing to 9920KiB

 Performance counter stats for 'mount -t jffs2 /dev/mtdblock7 /mnt':

         75.223488 task-clock                #    0.736 CPUs utilized          
                17 context-switches          #    0.226 K/sec                  
                 0 cpu-migrations            #    0.000 K/sec                  
                94 page-faults               #    0.001 M/sec                  
         100815917 cycles                    #    1.340 GHz                    
          16561335 stalled-cycles-frontend   #   16.43% frontend cycles idle   
           2991700 stalled-cycles-backend    #    2.97% backend  cycles idle   
         106536662 instructions              #    1.06  insns per cycle        
                                             #    0.16  stalled cycles per insn
          10931326 branches                  #  145.318 M/sec                   [ 4.13%]
            931410 branch-misses             #    8.52% of all branches         [ 2.87%]

       0.102157784 seconds time elapsed


I'm not sure this tells us very much. If anything it looks like not much has changes.

Daniel

  reply	other threads:[~2018-11-12 21:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-06 21:49 Nikunj Kela
2018-11-07  9:05 ` David Woodhouse
2018-11-07  9:16   ` Joakim Tjernlund
2018-11-07 16:12     ` David Woodhouse
2018-11-07 17:33       ` Daniel Walker
2018-11-07 17:58         ` David Woodhouse
2018-11-07 18:41           ` Joakim Tjernlund
2018-11-08 15:25             ` Christoph Hellwig
2018-11-07 19:21           ` Daniel Walker
2018-11-07 18:04   ` Nikunj Kela (nkela)
2018-11-07 18:14     ` Richard Weinberger
2018-11-08  8:11       ` David Woodhouse
2018-11-08 18:01         ` Nikunj Kela (nkela)
2018-11-08 18:50           ` Joakim Tjernlund
2018-11-08 19:47           ` David Woodhouse
2018-11-12 21:43             ` Daniel Walker [this message]
2018-11-12 22:50               ` Daniel Walker
2018-11-12 23:11                 ` David Woodhouse
2018-11-12 23:40                   ` Daniel Walker
2018-11-12 23:43                     ` David Woodhouse
2018-11-13  0:06                       ` Daniel Walker
2018-11-13 21:01                       ` Daniel Walker

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=20181112214333.lplffcc722hta43v@zorba \
    --to=danielwa@cisco.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=nkela@cisco.com \
    --cc=richard.weinberger@gmail.com \
    --cc=xe-linux-external@cisco.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

all inboxes | Powered by JetHome®