All of lore.kernel.org
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, bert hubert <ahu@ds9a.nl>,
	"M. Edward Borasky" <znmeb@aracnet.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Have the 2.4 kernel memory management problems on large machines been fixed?
Date: Wed, 22 May 2002 17:46:14 -0400	[thread overview]
Message-ID: <20020522174614.B2819@redhat.com> (raw)
In-Reply-To: <E17AXWu-0001vL-00@the-village.bc.nu> <1404136612.1022057787@[10.10.2.3]>

On Wed, May 22, 2002 at 08:56:28AM -0700, Martin J. Bligh wrote:
> > 7.3 has some of what is needed but not all. 
> 
> Can you outline the changes in this area? I want to make sure we're
> not all fighting the same problems seperately ;-) I know bounce
> buffers is one large element of that, though I believe you still
> only go up to 4Gb, unless I'm mistaken?

Yes, it only goes up to 4Gb.  It's because of the error handling code in 
the SCSI mid-layer and above, it fails to properly handle the >4gb sg 
entries on error conditions.  I'm working on that now and should have it 
fixed soon.

-- 
  Doug Ledford <dledford@redhat.com>     919-754-3700 x44233
         Red Hat, Inc. 
         1801 Varsity Dr.
         Raleigh, NC 27606
  

  parent reply	other threads:[~2002-05-22 21:46 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  6:51 2.4.19pre*: IO statistics in /proc/partitions corrupt Jochen Suckfuell
2002-05-22 14:00 ` Have the 2.4 kernel memory management problems on large machines been fixed? M. Edward Borasky
2002-05-22 14:08   ` bert hubert
2002-05-22 14:55     ` Alan Cox
2002-05-22 15:56       ` Martin J. Bligh
2002-05-22 16:23         ` Alan Cox
2002-05-22 21:46         ` Doug Ledford [this message]
2002-05-22 14:36   ` William Lee Irwin III
2002-05-22 15:44     ` Martin J. Bligh
2002-05-22 15:53       ` Martin J. Bligh
2002-05-22 16:07       ` William Lee Irwin III
2002-05-22 16:36         ` Martin J. Bligh
2002-05-22 17:21           ` Andrea Arcangeli
2002-05-22 18:18             ` Martin J. Bligh
2002-05-22 18:02         ` Alan Cox
2002-05-22 18:08           ` Linus Torvalds
2002-05-22 18:30             ` Rik van Riel
2002-05-22 18:40               ` Linus Torvalds
2002-05-22 18:48               ` Martin J. Bligh
2002-05-22 18:34             ` Have the 2.4 kernel memory management problems on large machines Alan Cox
2002-05-22 18:27               ` Linus Torvalds
2002-05-22 20:30             ` Have the 2.4 kernel memory management problems on large machines been fixed? William Lee Irwin III
2002-05-22 21:18               ` Martin J. Bligh
2002-05-22 21:23                 ` Linus Torvalds
2002-05-22 22:35                   ` Andrea Arcangeli
2002-05-22 22:44                   ` Martin J. Bligh
2002-05-28  2:08                 ` Wim Coekaerts
2002-05-31 20:39                   ` Andrea Arcangeli
2002-05-23 14:16             ` Bill Davidsen
2002-05-23 17:18               ` Linus Torvalds
2002-05-23 19:34                 ` Bill Davidsen
2002-05-23 19:46                   ` Linus Torvalds
2002-05-22 18:38           ` Martin J. Bligh
2002-05-22 17:50       ` Alan Cox
2002-05-22 17:54         ` J Sloan
2002-05-22 18:22           ` Have the 2.4 kernel memory management problems on large machines Alan Cox
2002-05-22 22:14             ` J Sloan
2002-05-22 18:24         ` Have the 2.4 kernel memory management problems on large machines been fixed? Martin J. Bligh
2002-05-22 22:05           ` Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2002-05-22 14:29 Alastair Stevens
     [not found] <E17AaR0-0002QM-00@the-village.bc.nu.suse.lists.linux.kernel>
     [not found] ` <Pine.LNX.4.33.0205221048570.23621-100000@penguin.transmeta.com.suse.lists.linux.kernel>
2002-05-22 20:23   ` Andi Kleen
2002-05-22 20:58     ` Linus Torvalds
2002-05-23 12:40       ` Mike Jagdis

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=20020522174614.B2819@redhat.com \
    --to=dledford@redhat.com \
    --cc=Martin.Bligh@us.ibm.com \
    --cc=ahu@ds9a.nl \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=znmeb@aracnet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.