mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: arjan@fenrus.demon.nl
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org, zaitcev@redhat.com
Subject: Re: Patch to split kmalloc in sd.c in 2.4.18+
Date: Sat, 23 Mar 2002 14:01:31 GMT	[thread overview]
Message-ID: <200203231401.g2NE1VU05526@fenrus.demon.nl> (raw)
In-Reply-To: <3C9C80AA.1080800@evision-ventures.com>

In article <3C9C80AA.1080800@evision-ventures.com> you wrote:
> Pete Zaitcev wrote:
>> Hello:
>> 
>> One problem I see when trying to use a box with 128 SCSI disks
>> is that sd_mod sometimes refuses to load. Earlier kernels simply
>> oopsed when it happened, but that is fixed in 2.4.18. The root
>> of the evil is the enormous array sd[] that sd_init allocates.
>> Alan suggested to split the allocation, which is what I did.
>> 
>> Arjan said that it may be easier to use vmalloc, and sure it is.
>> However, I heard that vmalloc space is not too big, so it may
>> make sense to conserve it (especially on non-x86 32-bitters).
> 
> kmalloc is spare - the vmalloc space is *HUUUUUGE*.

64Mb (effective usable size) is HUGE. sure. but you share it
with all other vmalloc users. I agree with Pete that kmalloc is the
superior solution; I mentioned vmalloc to him before because that would
have been the minimal fix; Pete decided to fix it for real... 
(also vmalloc is also rather slow for hotpaths due to tlb effects)

  reply	other threads:[~2002-03-23 14:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-23  2:58 Pete Zaitcev
2002-03-23 13:18 ` Martin Dalecki
2002-03-23 14:01   ` arjan [this message]
2002-03-23 17:07 ` Douglas Gilbert
2002-03-23 18:46   ` Eric Youngdale
2002-03-23 19:37   ` Pete Zaitcev
2002-03-23 20:03     ` Richard Gooch
2002-03-24  4:12     ` Douglas Gilbert
2002-03-24  5:16       ` Andre Hedrick
2002-03-24  5:38       ` Pete Zaitcev

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=200203231401.g2NE1VU05526@fenrus.demon.nl \
    --to=arjan@fenrus.demon.nl \
    --cc=dalecki@evision-ventures.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zaitcev@redhat.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

all inboxes | Powered by JetHome®