public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Piotr Hosowicz <piotr@hosowicz.com>
To: sedat.dilek@gmail.com
Cc: Sedat Dilek <sedat.dilek@googlemail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for December 27
Date: Tue, 28 Dec 2010 15:27:13 +0100	[thread overview]
Message-ID: <4D19F3C1.8010208@example.com> (raw)
In-Reply-To: <AANLkTim1Cj1rbgnFr6C7==UP+jiriJ55Kcu9wmgd+DKh@mail.gmail.com>

On 27.12.2010 17:16, Sedat Dilek wrote:
> 2010/12/27 Piotr Hosowicz<piotr@hosowicz.com>:
>> On 27.12.2010 16:13, Piotr Hosowicz wrote:
>>>
>>> On 27.12.2010 16:08, Sedat Dilek wrote:
>>>>
>>>> 2010/12/27 Piotr Hosowicz<piotr@hosowicz.com>:
>>>>>
>>>>> On 27.12.2010 15:48, Sedat Dilek wrote:
>>>>>>
>>>>>> 2010/12/27 Piotr Hosowicz<piotr@hosowicz.com>:
>>>>>>>
>>>>>>> On 27.12.2010 07:04, Stephen Rothwell wrote:
>>>>>>>
>>>>>>> Hello,
>>>>>>>
>>>>>>> I noticed that after first reboot with this kernel that my MP3
>>>>>>> collection
>>>>>>> in
>>>>>>> mocp layed on Ext4 fs opens painfully slow. It is not my mistake,
>>>>>>> because
>>>>>>> I
>>>>>>> always do it the same way, new kernel, then music on. The problem
>>>>>>> is not
>>>>>>> present in rc7-git4. I could measure it in some way (timing ls -la
>>>>>>> in tht
>>>>>>> dir?) if somebody needs it.
>>>>>>>
>>>>>>> Regards,
>>>>>>>
>>>>>>> Piotr Hosowicz
>>>>>>>
>>>>>>
>>>>>> You tried mblk_io_submit mount-option for that partition?
>>>>>
>>>>> No, I do not use it, I do not even know what it is. My options are:
>>>>>
>>>>> /dev/sda2 on / type ext4 (rw,errors=remount-ro)
>>>>>
>>>>
>>>> Have a closer look at "ext4: Turn off multiple page-io submission by
>>>> default"
>>>
>>> I tried to Google for mblk_io_submit but I didn't find anything helpful.
>>> Could you tell me how should I add this option in fstab and what will be
>>> its effect?
>>
>> As far as I understand that option regards writing, not reading. The
>> symptoms I described occured while reading only.
>>
>
> That's the only performance issue I am aware of in ext4 in recent time.
> Why don't you try it and present some numbers in transfer ratio (write, read)?

Ok, I'll try to measure it in shell. Now I am building newest non-next 
kernel and the trial script is:

#!/bin/bash

uname -a
mount
cd /data/music
time ls -d *
cd -

This is basically what mocp does when it enters my music directory, 
apart from displaying the results in ncurses based UI. Then I'll reboot 
with next kernel and run it again. Will it do?

Regards,

Piotr Hosowicz

-- 
Ktoś zapukał do drzwi.
-Bormann - pomyślał Stirlitz
-Tak, to ja - pomyślał Bormann
NP: Peter Green Splinter Group - Madison Blues
NB: 2.6.37-rc7-20101227-pztidm+

  reply	other threads:[~2010-12-28 14:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-27  6:04 linux-next: Tree for December 27 Stephen Rothwell
2010-12-27  8:04 ` Sedat Dilek
2010-12-27  9:11   ` Stephen Rothwell
2010-12-27  9:55     ` Sedat Dilek
2010-12-27 12:09       ` Sedat Dilek
2010-12-27 11:38 ` Mark Brown
2010-12-27 15:20   ` Stephen Rothwell
2010-12-27 15:38     ` Mark Brown
2010-12-27 14:36 ` Piotr Hosowicz
2010-12-27 14:48   ` Sedat Dilek
2010-12-27 14:57     ` Piotr Hosowicz
2010-12-27 15:08       ` Sedat Dilek
2010-12-27 15:13         ` Piotr Hosowicz
2010-12-27 15:45           ` Piotr Hosowicz
2010-12-27 16:16             ` Sedat Dilek
2010-12-28 14:27               ` Piotr Hosowicz [this message]
2010-12-28 15:09                 ` Piotr Hosowicz
2010-12-27 19:21 ` linux-next: Tree for December 27 (drivers/target/) Randy Dunlap
2010-12-27 22:47   ` Nicholas A. Bellinger
2010-12-27 19:55 ` [PATCH -next] ocfs2: fix build for OCFS2_FS_STATS not enabled Randy Dunlap
2010-12-27 20:52   ` Joel Becker
2010-12-27 21:41     ` Randy Dunlap
2010-12-27 19:57 ` linux-next: Tree for December 27 (drivers/target) Randy Dunlap
2010-12-27 22:49   ` Nicholas A. Bellinger
2010-12-28 15:08     ` James Bottomley

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=4D19F3C1.8010208@example.com \
    --to=piotr@hosowicz.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    --cc=sedat.dilek@googlemail.com \
    --cc=sfr@canb.auug.org.au \
    /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