From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Gibson <david@gibson.dropbear.id.au>,
Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
kvm@vger.kernel.org, Eric Auger <eric.auger@redhat.com>
Subject: Re: [RFC PATCH kernel] vfio-pci: Allow write combining
Date: Thu, 30 Nov 2017 14:06:39 -0600 [thread overview]
Message-ID: <1512072399.2224.22.camel@kernel.crashing.org> (raw)
In-Reply-To: <20171130042003.GW3023@umbus.fritz.box>
On Thu, 2017-11-30 at 15:20 +1100, David Gibson wrote:
> > > > This isn't at the top of my priority list to figure out the solution,
> > > > so whoever implements it will need to provide justification as they
> > > > move down the list from more to less preferred solutions. Thanks,
> > >
> > > I am trying... I was really counting on you guys having this discussed in
> > > Prague :(
> >
> > Should have been there to push your agenda... Thanks,
>
> We discussed it briefly, BenH seemed to think there wasn't a big
> difficulty, IIRC, which is why we didn't spend much time on this
> (compared to the other issues). So, talk to him.
Well, first we established that this wasn't an issue for KVM, so the
importance/urgency went down. It's still useful for DPDK.
Then we discussed quickly the various options, none of them is
particularily *difficult* as in the implementation is rather trivial,
the question is to chose which interface to provide userspace.
I don't have a strong opinion there. The mm guys might object to
hijacking MAP_NONBLOCK, otherwise that seems like the best approach, so
we should run that past them.
Cheers,
Ben.
next prev parent reply other threads:[~2017-11-30 20:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-09 2:50 [RFC PATCH kernel] vfio-pci: Allow write combining Alexey Kardashevskiy
2017-10-10 21:55 ` Alex Williamson
2017-10-11 2:05 ` Alexey Kardashevskiy
2017-10-11 2:42 ` Alex Williamson
2017-10-11 2:56 ` Alexey Kardashevskiy
2017-10-11 15:35 ` Benjamin Herrenschmidt
2017-10-16 5:54 ` Alexey Kardashevskiy
2017-10-16 6:00 ` David Gibson
2017-10-16 7:36 ` Alexey Kardashevskiy
2017-10-16 8:01 ` David Gibson
2017-11-06 5:44 ` Alexey Kardashevskiy
2017-11-14 2:23 ` David Gibson
2017-11-14 2:29 ` Benjamin Herrenschmidt
2017-11-14 16:28 ` Alex Williamson
2017-11-24 4:58 ` Alexey Kardashevskiy
2017-11-29 18:47 ` Alex Williamson
2017-11-30 4:20 ` David Gibson
2017-11-30 20:06 ` Benjamin Herrenschmidt [this message]
2017-10-16 8:38 ` Benjamin Herrenschmidt
2017-10-16 11:11 ` Alexey Kardashevskiy
2017-10-18 7:33 ` Benjamin Herrenschmidt
2017-10-18 9:00 ` Alexey Kardashevskiy
2017-10-18 14:21 ` Benjamin Herrenschmidt
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=1512072399.2224.22.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=eric.auger@redhat.com \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.