From: Anton Blanchard <anton@samba.org>
To: Jens Axboe <axboe@suse.de>
Cc: Paul Larson <plars@austin.ibm.com>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@transmeta.com>
Subject: Re: Scsi problems in 2.5.1-pre9
Date: Wed, 12 Dec 2001 08:28:02 +1100 [thread overview]
Message-ID: <20011211212802.GA30520@krispykreme> (raw)
In-Reply-To: <1008065277.25964.5.camel@plars.austin.ibm.com> <20011211164744.GC13498@suse.de> <20011211165426.GD13498@suse.de>
In-Reply-To: <20011211165426.GD13498@suse.de>
Hi Jens,
> > > Incorrect number of segments after building list
> > > counted 11, received 7
> >
> > Attached patch should fix it.
I just booted 2.5.1-pre10 on ppc64 and still get the errors:
Incorrect number of segments after building list
counted 3, received 2
req nr_sec 24, cur_nr_sec 8
This seems to be happening because we now allow sg merging through
the BIOVEC_MERGEABLE macro. On ppc64 (and sparc64) we can coalesce two
sg entries if the first one ends on a page boundary and the next one
starts on a page boundary because we have an IO MMU. (I know that you
know this, Im just explaining it for those who dont :)
Should we just remove the warning now?
Anton
next prev parent reply other threads:[~2001-12-11 21:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-11 10:07 Scsi problems in 2.5.1-pre9 Paul Larson
2001-12-11 16:05 ` Jens Axboe
2001-12-11 16:19 ` Jens Axboe
2001-12-11 10:34 ` Paul Larson
2001-12-11 16:30 ` Jens Axboe
2001-12-11 16:47 ` Jens Axboe
2001-12-11 16:54 ` Jens Axboe
2001-12-11 21:28 ` Anton Blanchard [this message]
2001-12-11 22:04 ` David S. Miller
2001-12-11 22:17 ` Anton Blanchard
2001-12-11 22:27 ` David S. Miller
2001-12-12 9:02 ` Jens Axboe
2001-12-12 9:15 ` David S. Miller
2001-12-12 9:21 ` Jens Axboe
2001-12-12 9:31 ` David S. Miller
2001-12-12 9:32 ` Jens Axboe
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=20011211212802.GA30520@krispykreme \
--to=anton@samba.org \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=plars@austin.ibm.com \
--cc=torvalds@transmeta.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