LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Mike Marion <mmarion@qualcomm.com>, NeilBrown <neilb@suse.com>
Cc: autofs mailing list <autofs@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored
Date: Wed, 29 Nov 2017 10:28:56 +0800 [thread overview]
Message-ID: <1be75afb-8702-d60c-5ecb-10ddd2edc062@themaw.net> (raw)
In-Reply-To: <20171129021354.GB2873@qualcomm.com>
On 29/11/17 10:13, Mike Marion wrote:
> On Wed, Nov 29, 2017 at 12:17:27PM +1100, NeilBrown wrote:
>
>> How big do people see /proc/self/mount* getting? What size reads
>> does 'strace' show the various programs using to read it?
>
> We already have line counts into 5 figures. This wasn't an issue until
> the change of /etc/mtab to a link. The large count is due to our large
> direct automount maps.
>
And, admittedly, the testing I was doing was with 15k+ size maps.
Of course it's necessary to have this number of mounts to see serious
problems which is easiest to do with large direct mount maps.
The thing that's different now is that before applications started
using /proc directly for mount table information using mount(2)
instead of mount(8) was enough to prevent the mount entries from
being added to the table seen by applications.
Ian
next prev parent reply other threads:[~2017-11-29 2:29 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 4:18 [PATCH 1/3] autofs - make disc device user accessible Ian Kent
2017-05-10 4:18 ` [PATCH 2/3] autofs - make dev ioctl version and ismountpoint " Ian Kent
2017-05-10 4:18 ` [PATCH 3/3] autofs - fix AT_NO_AUTOMOUNT not being honored Ian Kent
2017-05-12 12:49 ` Colin Walters
2017-11-21 1:53 ` NeilBrown
2017-11-22 4:28 ` Ian Kent
2017-11-23 0:36 ` Ian Kent
2017-11-23 2:21 ` NeilBrown
2017-11-23 2:46 ` Ian Kent
2017-11-23 3:04 ` Ian Kent
2017-11-23 4:49 ` NeilBrown
2017-11-23 6:34 ` Ian Kent
2017-11-27 16:01 ` Mike Marion
2017-11-27 23:43 ` Ian Kent
2017-11-28 0:29 ` Mike Marion
2017-11-29 1:17 ` NeilBrown
2017-11-29 2:13 ` Mike Marion
2017-11-29 2:28 ` Ian Kent [this message]
2017-11-29 2:48 ` NeilBrown
2017-11-29 3:14 ` Ian Kent
2017-11-29 2:56 ` Ian Kent
2017-11-29 3:45 ` NeilBrown
2017-11-29 6:00 ` Ian Kent
2017-11-29 7:39 ` NeilBrown
2017-11-30 0:00 ` Ian Kent
2017-11-29 16:51 ` Mike Marion
2017-11-23 0:47 ` NeilBrown
2017-11-23 1:43 ` Ian Kent
2017-11-23 2:26 ` Ian Kent
2017-11-23 3:04 ` NeilBrown
2017-11-23 3:41 ` Ian Kent
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=1be75afb-8702-d60c-5ecb-10ddd2edc062@themaw.net \
--to=raven@themaw.net \
--cc=autofs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarion@qualcomm.com \
--cc=neilb@suse.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 NNTP newsgroup(s).