From: Steve Lord <lord@sgi.com>
To: Jens Axboe <axboe@suse.de>
Cc: martin@dalecki.de,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: A new ide warning message
Date: 02 Aug 2002 08:50:55 -0500 [thread overview]
Message-ID: <1028296255.30192.9.camel@jen.americas.sgi.com> (raw)
In-Reply-To: <20020802124139.GR3010@suse.de>
On Fri, 2002-08-02 at 07:41, Jens Axboe wrote:
>
> Yeah it's a request for data, what else could it be? That's the only
> place where we call blk_rq_map_sg().
>
> Stephen, please provoke with this patch applied. I hope it works, it's
> untested :-)
>
Consider it provoked, I added a trace to the submit_bio call in XFS
as well, dumping sector number, bio length in bytes and number of
vector elements submitted:
submit_bio(READ, sector 0x414870, len 65536 vec_len 16
submit_bio(READ, sector 0x4148f0, len 65536 vec_len 16
pcidma: build 2 segments, supplied 1/16, sectors 128/8
bio 0: phys 1, hw 16
segment 0: phys 69599232, size 4096
segment 1: phys 69603328, size 4096
segment 2: phys 69607424, size 4096
segment 3: phys 69611520, size 4096
segment 4: phys 69615616, size 4096
segment 5: phys 69619712, size 4096
segment 6: phys 69623808, size 4096
segment 7: phys 69627904, size 4096
segment 8: phys 69632000, size 4096
segment 9: phys 69636096, size 4096
segment 10: phys 69640192, size 4096
segment 11: phys 69644288, size 4096
segment 12: phys 69648384, size 4096
segment 13: phys 69652480, size 4096
segment 14: phys 69656576, size 4096
segment 15: phys 69660672, size 4096
pcidma: build 2 segments, supplied 1/16, sectors 128/8
bio 0: phys 1, hw 16
segment 0: phys 69664768, size 4096
segment 1: phys 69668864, size 4096
segment 2: phys 69672960, size 4096
segment 3: phys 69677056, size 4096
segment 4: phys 69681152, size 4096
segment 5: phys 69685248, size 4096
segment 6: phys 69689344, size 4096
segment 7: phys 69693440, size 4096
segment 8: phys 69697536, size 4096
segment 9: phys 69701632, size 4096
segment 10: phys 69705728, size 4096
segment 11: phys 69709824, size 4096
segment 12: phys 69713920, size 4096
segment 13: phys 69718016, size 4096
segment 14: phys 69722112, size 4096
segment 15: phys 69726208, size 4096
And so on.....
The bio size being used is based purely on the BIO_MAX_SECTORS
constant, same code as ll_rw_kio. Looks like the direct I/O
path uses similar math.
Steve
--
Steve Lord voice: +1-651-683-3511
Principal Engineer, Filesystem Software email: lord@sgi.com
next prev parent reply other threads:[~2002-08-02 13:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 11:34 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
2002-08-02 12:41 ` Jens Axboe
2002-08-02 13:50 ` Steve Lord [this message]
2002-08-02 18:34 ` Bartlomiej Zolnierkiewicz
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=1028296255.30192.9.camel@jen.americas.sgi.com \
--to=lord@sgi.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®