From: Magnus Damm <magnus.damm@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: SH Core Linux 20110317
Date: Thu, 17 Mar 2011 11:21:36 +0000 [thread overview]
Message-ID: <AANLkTimZd0ac9c4qaJHndzZ-f=4omQkHs49jKuVhjSGE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikhuHy8iZO+K6OOARG7fAt90hXbcEFE91dirMOX@mail.gmail.com>
On Thu, Mar 17, 2011 at 4:55 PM, Mike Frysinger <vapier@gentoo.org> wrote:
> On Thursday, March 17, 2011 03:10:41 Magnus Damm wrote:
>> On Thu, Mar 17, 2011 at 3:56 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>> > i wonder if there's some way we can centralize/focus efforts on the Linux
>> > side so each SoC vendor doesnt keep coming up with its own magic sauce
>> > to glue worlds together. i really dont see this as being a useful area
>> > for everyone to "innovate" on their own. the advantage to being the
>> > first one into mainline is that everyone else will have to migrate to it
>> > :).
>> >
>> > perhaps start a list on vger.kernel.org and a wiki on wiki.kernel.org ?
>>
>> I believe the answer to all this is Virtio, but I'm not sure if
>> everyone will agree with me. =)
>
> so if i had to summarize your SuperH effort, it'd be "use virtio" ? i can
> work with that and see about driving stuff internally in that direction.
Yes! It would be great to see other vendors using Virtio.
I have not done any performance tuning yet though, so I guess the only
unknown factor is the overhead. But since Virtio is already used in
virtualized environments I believe that some optimization has been
done already. If that's not enough then future virtio specific driver
optimizations can be benefit both enterprise and embedded.
Thanks,
/ magnus
prev parent reply other threads:[~2011-03-17 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 6:40 SH Core Linux 20110317 Magnus Damm
2011-03-17 6:56 ` Mike Frysinger
2011-03-17 7:10 ` Magnus Damm
2011-03-17 7:55 ` Mike Frysinger
2011-03-17 11:21 ` Magnus Damm [this message]
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='AANLkTimZd0ac9c4qaJHndzZ-f=4omQkHs49jKuVhjSGE@mail.gmail.com' \
--to=magnus.damm@gmail.com \
--cc=linux-sh@vger.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;
as well as URLs for NNTP newsgroup(s).