public inbox for frysk@sourceware.org
 help / color / mirror / Atom feed
From: Mike Cvet <mcvet@redhat.com>
To: Phil Muldoon <pmuldoon@redhat.com>
Cc: frysk <frysk@sourceware.org>
Subject: Re: uslurp change
Date: Wed, 18 Jul 2007 18:25:00 -0000	[thread overview]
Message-ID: <469E5AFB.2030802@redhat.com> (raw)
In-Reply-To: <469D275C.9010108@redhat.com>

Phil Muldoon wrote:
> uslurp is a "special case" function for /proc/$$/maps which can be 
> large. It does the realloc dance on multiple 4k page reads while slurp 
> just reads one page from /proc. The older slurp still does the vast 
> majority of reads from /proc, so this optimization will be needed 
> there to. I cannot think of a reason why I just did not replace uslurp 
> with slurp many moons ago, but thinking about it, it probably should.
>

The update has been added to slurp() and slurp_thread() as well, through 
a new method in Errno.cxx called tryOpen().

- Mike

      reply	other threads:[~2007-07-18 18:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 20:25 Mike Cvet
2007-07-17 20:32 ` Phil Muldoon
2007-07-18 18:25   ` Mike Cvet [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=469E5AFB.2030802@redhat.com \
    --to=mcvet@redhat.com \
    --cc=frysk@sourceware.org \
    --cc=pmuldoon@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).