kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: manishrma@gmail.com (mani)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Changes in block layer for IOScheduler Insertion selection
Date: Mon, 30 May 2011 10:53:16 +0530	[thread overview]
Message-ID: <BANLkTikiupHHuAQd-z0dBBRzhrb5=49TqA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin-GHB0OtQiNt8sDtMczw86pnoLRQ@mail.gmail.com>

Dear Eduardo,

   I am using squashfs filesystem. So i am more concern with the read speed.
    whereas below are the details
                                                     read speed   write
speed
    ELEVATOR_INSERT_SORT       8 MBps            5MBps
    ELEVATOR_INSERT_BACK      10 MBps           7.2MBps

   used the following command for measurement for both the cases.
   reading
   hdparm -t /dev/mtdblock3

   writing
   dd if=/dev/zero of=/dev/mtd3 bs=4096 count=100k

   As of now everything is working fine with those changes
   but i am worried if these changes would have any adverse effect anywhere
?

   Thanks.


On Fri, May 27, 2011 at 8:37 PM, Eduardo Silva <edsiper@gmail.com> wrote:

> On Fri, May 27, 2011 at 8:29 AM, mani <manishrma@gmail.com> wrote:
> >
> > Dear All,
> >
> > I am working on linux kernel 2.6.32.9 tegra NVIDIA board.
> >
> > I am getting ~8MBps speed of the Nand disk if i use hdparm
> > hdparm -t /dev/mtdblock3
> >
> > i made changes in block layer of kernel as below:-
> >
> > block/blk-core.c
> > static inline void add_request(struct request_queue *q, struct request
> *req)
> > {
> >         drive_stat_acct(req, 1);
> >
> >         /*
> >          * elevator indicated where it wants this request to be
> >          * inserted at elevator_merge time
> >          */
> >
> >         __elv_add_request(q, req, ELEVATOR_INSERT_BACK, 0);
> >         //__elv_add_request(q, req, ELEVATOR_INSERT_SORT, 0);
> > }
> >
> >
>
> What are the results for read and write for both cases ?
>
>
> > changed ELEVATOR_INSERT_SORT to ELEVATOR_INSERT_BACK
> > it improves my NAND speed to 10MBps.
> >
> > I am using "noop" I/O scheduler.
> >
> > Will this change have any adverse effect in kernel ? or any other side
> > effect as far as i am using only Nand no Hard disk.
> >
> >
> > Thanks
> > Mani
> >
> >
> > _______________________________________________
> > Kernelnewbies mailing list
> > Kernelnewbies at kernelnewbies.org
> > http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
> >
> >
>
>
>
> --
> Eduardo Silva
> http://edsiper.linuxchile.cl
> http://www.monkey-project.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20110530/027b23f3/attachment.html 

  reply	other threads:[~2011-05-30  5:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTimLxWfO1hXzdROEJKx-CCMQBEXcHg@mail.gmail.com>
2011-05-27 12:29 ` Changes in block layer for IOScheduler Insertion selection mani
2011-05-27 15:07   ` Eduardo Silva
2011-05-30  5:23     ` mani [this message]
2011-06-02  3:41       ` mani
2012-02-06 18:49         ` Matthias Brugger

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='BANLkTikiupHHuAQd-z0dBBRzhrb5=49TqA@mail.gmail.com' \
    --to=manishrma@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).