From: Hans Reiser <reiser@namesys.com>
To: Christophe Saout <christophe@saout.de>
Cc: "Markus Törnqvist" <mjt@nysv.org>,
"Vladimir V. Saveliev" <vs@namesys.com>,
"David Dabbs" <david@dabbs.net>,
reiserfs-list@namesys.com
Subject: Re: mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error
Date: Wed, 04 Aug 2004 16:57:21 -0700 [thread overview]
Message-ID: <411177E1.1040209@namesys.com> (raw)
In-Reply-To: <1091659605.8276.3.camel@leto.cs.pocnet.net>
Christophe Saout wrote:
>Am Mittwoch, den 04.08.2004, 14:47 -0700 schrieb Hans Reiser:
>
>
>
>>V4 likes stack. If someone can convince me that kmalloc is as efficient
>>as stack, I'd like to hear it, because I know I lack expertise on the topic.
>>
>>
>
>The disassembled fast path of kmalloc (with a size of the object known
>at compile time) fits on one page. Most of the time it will just return
>a pointer from a pool of cached and cache-hot objects.
>
>
>
whereas using stack is 0 instructions or?
next prev parent reply other threads:[~2004-08-04 23:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 6:55 mongo_copy: cp: cannot stat `/mnt/testfs/testdir0-0-0/f92': Input/output error David Dabbs
2004-08-04 8:40 ` Hans Reiser
2004-08-04 8:51 ` Vladimir V. Saveliev
2004-08-04 8:59 ` Hans Reiser
2004-08-04 12:51 ` Vladimir V. Saveliev
2004-08-04 18:38 ` mjt
2004-08-04 21:47 ` Hans Reiser
2004-08-04 22:46 ` Christophe Saout
2004-08-04 23:57 ` Hans Reiser [this message]
2004-08-05 0:06 ` Christophe Saout
2004-08-05 0:14 ` Lamont R. Peterson
2004-08-05 1:44 ` Hans Reiser
2004-08-05 2:24 ` Carl-Daniel Hailfinger
2004-08-05 13:38 ` Chris Mason
2004-08-04 14:14 ` David Dabbs
2004-08-04 17:38 ` Hans Reiser
2004-08-04 17:46 ` Chris Mason
2004-08-04 18:24 ` David Dabbs
2004-08-04 10:02 ` mjt
-- strict thread matches above, loose matches on Subject: below --
2004-08-04 17:41 David Dabbs
2004-08-04 18:11 ` Hans Reiser
2004-08-04 18:29 ` David Dabbs
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=411177E1.1040209@namesys.com \
--to=reiser@namesys.com \
--cc=christophe@saout.de \
--cc=david@dabbs.net \
--cc=mjt@nysv.org \
--cc=reiserfs-list@namesys.com \
--cc=vs@namesys.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 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.