All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oleg Drokin <green@linuxhacker.ru>
To: BlaisorBlade <blaisorblade_spam@yahoo.it>
Cc: jdike@karaya.com, user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [PATCH] Fix for annoying problem with hostfs readdir problems.
Date: Mon, 19 Apr 2004 01:26:20 +0300	[thread overview]
Message-ID: <20040418222620.GA1779@linuxhacker.ru> (raw)
In-Reply-To: <200404181726.23698.blaisorblade_spam@yahoo.it>

Hello!

On Sun, Apr 18, 2004 at 05:26:23PM +0200, BlaisorBlade wrote:
> > >    So the annoying problem with readdir not working on hostfs (on 2.6
> > > host kernel only for me) was finally hunted to memory allocation
> > >    problem during opendir.
> I've experienced it too onto 2.6 and someone else had the same problem - but 
> that patch is not perfect. Using always vmalloc() instead of kmalloc() is 
> wrong - vmalloc is slower, and Linus spoke against vmalloc(); it would also 
> slow down everything using malloc().

Well, speed is not of much an issue there, that function is only used for
glibc allocations. And that read_dir() is probably the only place that
causes glibc to allocate something.

> Probably you should use vmalloc() only if size is > the size limit (if this is 
> the problem, as I guess). When you come at free() it is a bit hard, but IIRC 
> vmalloc() can return pointers inside a certain, known memory area, right? So 
> it is possible to understand what function to call.

I am sure that all of the complexity you propose to implement won't pay off in
the end.

Bye,
    Oleg


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

      reply	other threads:[~2004-04-18 22:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-15 21:03 [uml-devel] [PATCH] Fix for annoying problem with hostfs readdir problems Oleg Drokin
2004-04-15 21:46 ` [uml-devel] " Oleg Drokin
2004-04-18 15:26   ` BlaisorBlade
2004-04-18 22:26     ` Oleg Drokin [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=20040418222620.GA1779@linuxhacker.ru \
    --to=green@linuxhacker.ru \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=jdike@karaya.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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.