From: "Seebs" <seebs@seebs.net>
To: "Richard Purdie" <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 2/4] pseudo: Ignore mismatched inodes from the db
Date: Tue, 29 Sep 2020 12:05:29 -0500 [thread overview]
Message-ID: <20200929120529.2bac3172@seebsdell> (raw)
In-Reply-To: <cef99332d290dc2fb0c39b8fa3ee022b64674ee6.camel@linuxfoundation.org>
On Mon, 28 Sep 2020 22:42:18 +0100
"Richard Purdie" <richard.purdie@linuxfoundation.org> wrote:
> It helps to know that! I wasn't sure if you'd hate the path filtering.
It was on my to-do list at one point to be able to denote "the pseudo
filesystem" in some way and just politely ignore everything outside it.
And, possibly, switch to keeping paths relative to it in some way.
But it looked very expensive, and honestly one of the things it was
waiting on was my vague belief that what pseudo really needs is to
switch to using length-prefixed strings so it can stop constantly
calling strlen.
-s
next prev parent reply other threads:[~2020-09-29 17:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-28 13:38 [PATCH 1/4] staging: Ensure cleaned dependencies are added Richard Purdie
2020-09-28 13:38 ` [PATCH 2/4] pseudo: Ignore mismatched inodes from the db Richard Purdie
2020-09-28 14:13 ` [OE-core] " Seebs
2020-09-28 14:51 ` Richard Purdie
2020-09-28 15:56 ` Seebs
2020-09-28 21:42 ` Richard Purdie
2020-09-29 17:05 ` Seebs [this message]
2020-09-28 13:38 ` [PATCH 3/4] pseudo: Add support for ignoring paths from the pseudo DB Richard Purdie
2020-09-28 13:38 ` [PATCH 4/4] base/bitbake.conf: Enable pseudo path filtering Richard Purdie
2020-09-28 15:15 ` [OE-core] [PATCH 1/4] staging: Ensure cleaned dependencies are added Christopher Larson
2020-09-28 17:03 ` Richard Purdie
2020-10-06 16:07 ` Chris Laplante
2020-10-06 16:49 ` Richard Purdie
2020-10-06 16:59 ` Chris Laplante
2020-10-07 10:29 ` Richard Purdie
2020-10-07 14:58 ` Chris Laplante
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=20200929120529.2bac3172@seebsdell \
--to=seebs@seebs.net \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
/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