From: Christoph Hellwig <hch@infradead.org>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] userspace infrastructure services
Date: Wed, 12 Aug 2015 11:21:03 -0700 [thread overview]
Message-ID: <20150812182103.GA20106@infradead.org> (raw)
In-Reply-To: <20150812111552.0f7e5fe7@urahara>
On Wed, Aug 12, 2015 at 11:15:52AM -0700, Stephen Hemminger wrote:
> I expected someone else to bring this topic up...
>
> One thing that is happening is that there is lots of activity in moving core features
> of the kernel into userspace (networking, storage, security). I don't want to get into
> an argument over whether that is good or bad;
Which I think is the most important question of them all. From all
the pain caused and the little gains I'm a believer it's mostly bad,
especially for cases like:
> The area I am most familiar with is the DPDK which has to have its own UIO drivers
> to work in all environments (get device into userspace). And then has to have its
> own drivers to simulate network device (put device back into kernel). This leads
> to unmanageable ABI and development technical debt.
Which interacts on both sides. In that case "let them suffer for their
stupidity" is the only valid answer.
For a case where it's more reasonable there might be a different answer.
next prev parent reply other threads:[~2015-08-12 18:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 18:15 Stephen Hemminger
2015-08-12 18:21 ` Christoph Hellwig [this message]
2015-08-12 18:38 ` James Bottomley
2015-08-13 15:40 ` Christoph Lameter
2015-08-12 18:46 ` Stephen Hemminger
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=20150812182103.GA20106@infradead.org \
--to=hch@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=stephen@networkplumber.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