public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Jens Axboe <axboe@suse.de>
Cc: "Justin T. Gibbs" <gibbs@scsiguy.com>,
	linux-kernel@vger.kernel.org, axel@pearbough.net
Subject: Re: drivers/scsi/aic7xxx/aic7xxx_osm.c: warning is error
Date: Wed, 14 May 2003 01:20:15 -0700	[thread overview]
Message-ID: <20030514082015.GI2444@holomorphy.com> (raw)
In-Reply-To: <20030514075407.GA10685@suse.de>

On Wed, May 14 2003, Mike Anderson wrote:
[...]
>> bounce_pfn: 0xfffff
[...]

That might explain the performance problem reported to me not long
after I posted the thing.

On Wed, May 14, 2003 at 09:54:07AM +0200, Jens Axboe wrote:
> So to recap, aic7xxx will never see a request that exceeds one of the
> above values. Total request size will always be equal to or below 4MiB,
> less than or equal to 128 segments, and will never cross a 4GB memory
> boundary. Memory above pfn 0xfffff (4GB) will be bounced, but this could
> be because that's just the amount of memory the box has you dumped this
> info from.

Hey, I got a bug report of a compile error and dove into bogus-looking
code around it meant to cater to antediluvian kernel versions and the
maintainer's preference for an identical driver across bunches of
kernel versions. I've heard the bit about the midlayer preventing these
conditions entirely a dozen times in the past 2 hours. =(

-- wli

  reply	other threads:[~2003-05-14  8:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-14  0:40 drivers/scsi/aic7xxx/aic7xxx_osm.c: warning is error axel
2003-05-14  1:29 ` William Lee Irwin III
2003-05-14  1:41   ` axel
2003-05-14  3:18 ` William Lee Irwin III
2003-05-14  4:57   ` William Lee Irwin III
2003-05-14  6:05   ` Justin T. Gibbs
2003-05-14  6:16     ` William Lee Irwin III
2003-05-14  7:37     ` Mike Anderson
2003-05-14  7:54       ` Jens Axboe
2003-05-14  8:20         ` William Lee Irwin III [this message]
2003-05-14 15:56         ` Mike Anderson

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=20030514082015.GI2444@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=axboe@suse.de \
    --cc=axel@pearbough.net \
    --cc=gibbs@scsiguy.com \
    --cc=linux-kernel@vger.kernel.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