public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Ilia Mirkin <imirkin@alum.mit.edu>, Dave Hansen <dave@sr71.net>
Cc: dave.hansen@linux.intel.com, john@johnmccutchan.com,
	rlove@rlove.org, eparis@parisplace.org, viro@zeniv.linux.org.uk,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fs: inotify: systemd needs it so make it depend on CONFIG_EMBEDDED
Date: Fri, 19 Jun 2015 14:54:03 -0400	[thread overview]
Message-ID: <5584654B.6050500@gmail.com> (raw)
In-Reply-To: <CAKb7UvhFEGGwa63VmhrUYutwMoWYsHVRJ=5faXkcG5w3C9AM7w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1939 bytes --]

On 2015-06-19 14:18, Ilia Mirkin wrote:
> On Fri, Jun 19, 2015 at 2:07 PM, Dave Hansen <dave@sr71.net> wrote:
>>
>> From: Dave Hansen <dave.hansen@linux.intel.com>
>>
>> I have a little microbenchmark that sits and does write() in a loop.
>> The number one kernel function in the profiles is __srcu_read_lock()
>> from fsnotify().  I decided to turn off INOTIFY in order to see what
>> the potential from optimizing this path would be.  I ended up with
>> a system at the rescue console as systemd complained that dependencies
>> were not met mounting some non-root filesystems:
>>
>>          systemd: inotify_init1() failed: Function not implemented
>>          systemd: Dependency failed for Mark the need to relabel after reboot.
>>          systemd: Triggering OnFailure= dependencies of local-fs.target.
>>          systemd: inotify_init1() failed: Function not implemented
>>          systemd: Dependency failed for /gcc.
>>
>> It looks like CONFIG_INOTIFY is now a critical part of any system
>> that wants to both use systemd and boot.  Let's make it depend
>> on CONFIG_EMBEDDED.
>
> Is systemd depending on something really reason enough to make it
> depend on EMBEDDED? For example all the cgroups stuff is not only not
> dependent on embedded, but also off by default, and I'm sure there are
> a boatload of other dependencies which any normal system has no
> business worrying about but that are required by systemd.
>
>    -ilia
I agree with this, kconfig isn't designed to make sure that your system 
will boot.  There are plenty of non-embedded systems that don't use 
systemd at all (such as every Linux based system on the TOP500 list, and 
a large majority of Gentoo installations), and also have no reason to 
have INOTIFY enabled.

I would stipulate however that systemd _should_ (if it doesn't already) 
clearly document this and any other kernel configuration dependencies.



[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2967 bytes --]

  reply	other threads:[~2015-06-19 18:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 18:07 [PATCH] fs: inotify: systemd needs it so make it depend on CONFIG_EMBEDDED Dave Hansen
2015-06-19 18:18 ` Ilia Mirkin
2015-06-19 18:54   ` Austin S Hemmelgarn [this message]
2015-06-19 21:48   ` Dave Hansen
2015-06-22 12:20     ` Austin S Hemmelgarn

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=5584654B.6050500@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=dave@sr71.net \
    --cc=eparis@parisplace.org \
    --cc=imirkin@alum.mit.edu \
    --cc=john@johnmccutchan.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlove@rlove.org \
    --cc=torvalds@linux-foundation.org \
    --cc=viro@zeniv.linux.org.uk \
    /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