mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anton Altaparmakov <aia21@cam.ac.uk>
To: Andrew Morton <akpm@osdl.org>
Cc: Zhonglin Zhang <zhonglinzh@mobilesoft.com.cn>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: a little improvement  for vmalloc
Date: Thu, 06 Jan 2005 09:26:41 +0000	[thread overview]
Message-ID: <1105003601.19888.2.camel@imp.csi.cam.ac.uk> (raw)
In-Reply-To: <20050105193827.12d83341.akpm@osdl.org>

On Wed, 2005-01-05 at 19:38 -0800, Andrew Morton wrote:
> Zhonglin Zhang <zhonglinzh@mobilesoft.com.cn> wrote:
> >
> > In FUNCTION __vmalloc ,
> > 
> >  There is a statement;
> > 
> >  if (!size || (size >> PAGE_SHIFT) > num_physpages)
> >          return NULL;
> 
> Probably the second part of the test should be removed.  If the requested
> area size is
> 
> a) less than the size of the vmalloc arena and
> 
> b) more than the number of allocatable pages
> 
> then yes, the machine will have a ton of trouble allocating the memory and
> will actually lock up.
> 
> But the only way that will happen is if some code is made to do a large
> number of smaller vmallocs.  Nobody does a huge single vmalloc like that.

I thought that second test was to avoid stupid bugs that may exist in
some random (perhaps ex-tree) modules that would otherwise cause the
machine to lockup...

Best regards,

        Anton
-- 
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK
Linux NTFS maintainer / IRC: #ntfs on irc.freenode.net
WWW: http://linux-ntfs.sf.net/ & http://www-stu.christs.cam.ac.uk/~aia21/


      reply	other threads:[~2005-01-06  9:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-06  3:18 Zhonglin Zhang
2005-01-06  3:38 ` Andrew Morton
2005-01-06  9:26   ` Anton Altaparmakov [this message]

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=1105003601.19888.2.camel@imp.csi.cam.ac.uk \
    --to=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zhonglinzh@mobilesoft.com.cn \
    /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®