From: Marcin Dalecki <dalecki@evision.ag>
To: Jens Axboe <axboe@suse.de>
Cc: martin@dalecki.de, Stephen Lord <lord@sgi.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A new ide warning message
Date: Fri, 02 Aug 2002 14:31:58 +0200 [thread overview]
Message-ID: <3D4A7BBE.90104@evision.ag> (raw)
In-Reply-To: 20020802123055.GQ3010@suse.de
Uz.ytkownik Jens Axboe napisa?:
>>*/
>>+ ch->max_segment_size = (1<<16) - 512;
>>
>>
>>I would in esp. like to see the result of setting ch->max_segment_size
>>= (1 << 15).
>
>
> This might not be such a good idea, since the limit-bio-size etc stuff
> isn't in yet, depending on _exactly_ how big the bio's xfs are building
> are. If they are max 8 pages (I seem to recall so), then yeah the above
> test would be nice to see. If they are bigger than 8 pages, then the
> above would be a meaningless test.
Sure. I'm aware of this. And I haven't looked at the XFS code
yet, so I can only guess about it.
What I can do myself is just pushing this limit even lower just to
see at which point my own system (ext3) starts to turn tits up ...
> I'll hack up a rq_dump() function to slap in pcidma.c as well.
Yes that would be a "nice to have too".
But it is a request for actual data as far as I can see.
next prev parent reply other threads:[~2002-08-02 12:33 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 11:34 A new ide warning message Stephen Lord
2002-08-02 11:38 ` Marcin Dalecki
2002-08-02 11:53 ` Jens Axboe
2002-08-02 11:59 ` Jens Axboe
2002-08-02 13:47 ` Bartlomiej Zolnierkiewicz
2002-08-02 14:20 ` Jens Axboe
2002-08-02 16:01 ` Bartlomiej Zolnierkiewicz
2002-08-02 16:11 ` Jens Axboe
2002-08-03 18:41 ` Marcin Dalecki
2002-08-02 11:47 ` Jens Axboe
2002-08-02 11:48 ` Marcin Dalecki
2002-08-02 11:55 ` Jens Axboe
2002-08-02 12:05 ` Stephen Lord
2002-08-02 12:12 ` Marcin Dalecki
2002-08-02 12:30 ` Jens Axboe
2002-08-02 12:31 ` Marcin Dalecki [this message]
2002-08-02 12:41 ` Jens Axboe
2002-08-02 13:50 ` Steve Lord
2002-08-02 18:34 ` Bartlomiej Zolnierkiewicz
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 3:28 Adam J. Richter
2002-08-03 3:32 Adam J. Richter
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=3D4A7BBE.90104@evision.ag \
--to=dalecki@evision.ag \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lord@sgi.com \
--cc=martin@dalecki.de \
/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