From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>
Subject: Re: [PATCH] perf: Move fs.* to generic lib/lk/
Date: Thu, 21 Nov 2013 12:05:24 -0300 [thread overview]
Message-ID: <20131121150524.GA24806@ghostprotocols.net> (raw)
In-Reply-To: <20131121120605.GC26009@pd.tnic>
Em Thu, Nov 21, 2013 at 01:06:05PM +0100, Borislav Petkov escreveu:
> On Thu, Nov 21, 2013 at 12:42:24PM +0100, Ingo Molnar wrote:
> > ... and just in case you are wondering why I'm making a fuss about it:
> > a naming discussion for something fundamental as this isn't bikeshed
> > painting, we really want people to look at that place to readily
> > stuff kernel related helpers into, and the name should make that very
> > obvious.
> No, I absolutely don't think it is a bikeshedding exercise too. We
> really need that lib because people have started growing their own
> facilities in tools/ and outside so having a lib which implements
> generic functionality for interfacing with the kernel right is going to
> save everyone a lot of time and energy.
> So kapi it is, I'm gonna convert what we have to it but leave time for
> acme to wake up and smell the coffee ... and the change :-)
I'm ok with having a library that has this mission statement:
"To offers various helper methods to interface with the Linux kernel:
debugfs, procfs, sysfs handling routines with no policy, just pure,
obvious helpers to use kernel functionality."
Naming is a bit hard, to keep it small, descriptive, as API can lead
people to think about other kinds of kernel APIs (syscalls?), "fskapi"
to mean "fs based kernel API" would perhaps be more descriptive? A
longer (more descriptive) possibility would be "linux-fskapi".
- Arnaldo
P.S.: "fskapi" also sounds, humm, fun ;-)
next prev parent reply other threads:[~2013-11-21 15:20 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 21:56 [PATCH] perf: Move fs.* to generic lib/lk/ Borislav Petkov
2013-11-21 7:34 ` Ingo Molnar
2013-11-21 10:07 ` Borislav Petkov
2013-11-21 11:17 ` Ingo Molnar
2013-11-21 11:30 ` Borislav Petkov
2013-11-21 11:42 ` Ingo Molnar
2013-11-21 12:06 ` Borislav Petkov
2013-11-21 12:39 ` Steven Rostedt
2013-11-21 13:49 ` Borislav Petkov
2013-11-21 13:56 ` Steven Rostedt
2013-11-21 14:18 ` Borislav Petkov
2013-11-21 15:12 ` Arnaldo Carvalho de Melo
2013-11-21 15:05 ` Arnaldo Carvalho de Melo [this message]
2013-11-21 15:28 ` Borislav Petkov
2013-11-21 17:37 ` Arnaldo Carvalho de Melo
2013-11-21 19:00 ` Borislav Petkov
2013-11-22 12:27 ` Ingo Molnar
2013-11-22 13:50 ` Borislav Petkov
2013-11-22 15:00 ` Arnaldo Carvalho de Melo
2013-11-22 15:20 ` David Ahern
2013-11-22 15:39 ` Ingo Molnar
2013-11-22 15:54 ` Ingo Molnar
2013-11-23 13:12 ` Borislav Petkov
2013-11-26 18:03 ` Ingo Molnar
2013-11-27 15:42 ` Borislav Petkov
2013-11-23 13:04 ` Borislav Petkov
2013-11-26 18:17 ` Ingo Molnar
2013-11-27 15:39 ` Borislav Petkov
2013-11-28 12:16 ` Borislav Petkov
2013-12-02 20:30 ` Arnaldo Carvalho de Melo
2013-11-22 14:57 ` Arnaldo Carvalho de Melo
2013-11-22 15:43 ` Ingo Molnar
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=20131121150524.GA24806@ghostprotocols.net \
--to=acme@infradead.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=rric@kernel.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