Bug 162706 - iscsi_sfnet driver uses bounce buffers when it does not need to on ia64
iscsi_sfnet driver uses bounce buffers when it does not need to on ia64
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: kernel (Show other bugs)
ia64 Linux
medium Severity medium
: ---
: ---
Assigned To: Mike Christie
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-07-07 17:18 EDT by Mike Christie
Modified: 2007-11-30 17:07 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-19 14:58:37 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Mike Christie 2005-07-07 17:18:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050524 Fedora/1.0.4-4 Firefox/1.0.4

Description of problem:
The iscsi_sfnet driver does not handle high mem becuase its kmap code is broken (it does a loop with multiple kmap without kunmapping). There is no HW limitation like with some real HW cards. For ia64 though, high mem is set but the kernel memory is mapped. Since the driver does not support high mem only becuase it needs to touch the buffers and to do so it will need to use kmap if the mem is not mapped for ia64 we incorrectly tell the block and scsi layer we need bounce buffers.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. setup iscsi on ia64
2. run IO to iscsi devices and see bounce buffers being used

Expected Results:  iscsi driver should not have used bounce buffers

Additional info:
Comment 1 RHEL Product and Program Management 2007-10-19 14:58:37 EDT
This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
For more information of the RHEL errata support policy, please visit:
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.