That is what I said. I am using vmalloc only. But the call to
vmalloc is hanging.

-hiren

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Monday, April 02, 2001 6:26 PM
> To: [EMAIL PROTECTED]
> Subject: RE: vmalloc on 2.4.x on ia64
> 
> 
> kmalloc() has a limit of 128KB.  Use get_free_pages() or 
> vmalloc() instead,
> or break up your allocation into smaller hunks.
> 
> Thanks,
> Matt
> 
> -- 
> Matt Domsch
> Sr. Software Engineer
> Dell Linux Systems Group
> Linux OS Development
> www.dell.com/linux
> 
> 
> 
> > -----Original Message-----
> > From: MEHTA,HIREN (A-SanJose,ex1) [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, April 02, 2001 7:07 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: vmalloc on 2.4.x on ia64
> > 
> > 
> > Greetings.
> > 
> > Is vmalloc() interface broken on any of 2.4.x kernel on ia64 ?
> > I am trying to call vmalloc from the driver to allocate
> > about 130kb of memory and it hangs the system.
> > I am running 2.4.1 kernel with ia64 patch (I can find out the
> > exact patch if needed) on LION. Let me know if more information
> > is required.
> > 
> > Thanks and regards,
> > -hiren
> > -
> > To unsubscribe from this list: send the line "unsubscribe 
> > linux-kernel" in
> > the body of a message to [EMAIL PROTECTED]
> > More majordomo info at  http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at  http://www.tux.org/lkml/
> > 
> > 
> 
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to