From: Dan Williams <dan.j.williams@intel.com> To: Nicholas Piggin <npiggin@gmail.com> Cc: "Luck, Tony" <tony.luck@intel.com>, Matthew Wilcox <mawilcox@microsoft.com>, Michael Ellerman <mpe@ellerman.id.au>, linux-nvdimm <linux-nvdimm@lists.01.org>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, Christoph Hellwig <hch@lst.de> Subject: Re: [RESEND 2/3] powerpc/memcpy: Add memcpy_mcsafe for pmem Date: Tue, 1 May 2018 13:57:13 -0700 [thread overview] Message-ID: <CAPcyv4hwb5ebVpYvAn+Bof_NxO6T3X1K+0B7Xbd07FrK8xZi7Q@mail.gmail.com> (raw) In-Reply-To: <CAPcyv4hQDetYZaQXHoD-L+KWrMJyypvHw=xzm7tb61qt9w=a3g@mail.gmail.com> On Thu, Apr 5, 2018 at 8:00 AM, Dan Williams <dan.j.williams@intel.com> wrote: > On Wed, Apr 4, 2018 at 11:45 PM, Nicholas Piggin <npiggin@gmail.com> wrote: [,,] >> What's the problem with just counting bytes copied like usercopy -- >> why is that harder than cacheline accuracy? >> >>> I'd rather implement the existing interface and port/support the new interface >>> as it becomes available >> >> Fair enough. > > I have patches already in progress to change the interface. My > preference is to hold off on adding a new implementation that will > need to be immediately reworked. When I say "immediate" I mean that > should be able to post what I have for review within the next few > days. > > Whether this is all too late for 4.17 is another question... Here is the x86 version of a 'bytes remaining' memcpy_mcsafe() implemenation: https://lists.01.org/pipermail/linux-nvdimm/2018-May/015548.html _______________________________________________ Linux-nvdimm mailing list Linux-nvdimm@lists.01.org https://lists.01.org/mailman/listinfo/linux-nvdimm
WARNING: multiple messages have this Message-ID (diff)
From: Dan Williams <dan.j.williams@intel.com> To: Nicholas Piggin <npiggin@gmail.com> Cc: Balbir Singh <bsingharora@gmail.com>, Michael Ellerman <mpe@ellerman.id.au>, linuxppc-dev <linuxppc-dev@lists.ozlabs.org>, linux-nvdimm <linux-nvdimm@lists.01.org>, Christoph Hellwig <hch@lst.de>, Matthew Wilcox <mawilcox@microsoft.com>, "Luck, Tony" <tony.luck@intel.com> Subject: Re: [RESEND 2/3] powerpc/memcpy: Add memcpy_mcsafe for pmem Date: Tue, 1 May 2018 13:57:13 -0700 [thread overview] Message-ID: <CAPcyv4hwb5ebVpYvAn+Bof_NxO6T3X1K+0B7Xbd07FrK8xZi7Q@mail.gmail.com> (raw) In-Reply-To: <CAPcyv4hQDetYZaQXHoD-L+KWrMJyypvHw=xzm7tb61qt9w=a3g@mail.gmail.com> On Thu, Apr 5, 2018 at 8:00 AM, Dan Williams <dan.j.williams@intel.com> wrote: > On Wed, Apr 4, 2018 at 11:45 PM, Nicholas Piggin <npiggin@gmail.com> wrote: [,,] >> What's the problem with just counting bytes copied like usercopy -- >> why is that harder than cacheline accuracy? >> >>> I'd rather implement the existing interface and port/support the new interface >>> as it becomes available >> >> Fair enough. > > I have patches already in progress to change the interface. My > preference is to hold off on adding a new implementation that will > need to be immediately reworked. When I say "immediate" I mean that > should be able to post what I have for review within the next few > days. > > Whether this is all too late for 4.17 is another question... Here is the x86 version of a 'bytes remaining' memcpy_mcsafe() implemenation: https://lists.01.org/pipermail/linux-nvdimm/2018-May/015548.html
next prev parent reply other threads:[~2018-05-01 20:57 UTC|newest] Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-04-04 23:19 [RESEND 0/3] Add support for memcpy_mcsafe Balbir Singh 2018-04-04 23:19 ` Balbir Singh 2018-04-04 23:19 ` [RESEND 1/3] powerpc/mce: Bug fixes for MCE handling in kernel space Balbir Singh 2018-04-04 23:19 ` Balbir Singh 2018-04-04 23:49 ` Nicholas Piggin 2018-04-04 23:49 ` Nicholas Piggin 2018-04-05 1:11 ` Balbir Singh 2018-04-05 1:11 ` Balbir Singh 2018-04-04 23:19 ` [RESEND 2/3] powerpc/memcpy: Add memcpy_mcsafe for pmem Balbir Singh 2018-04-04 23:19 ` Balbir Singh 2018-04-04 23:57 ` Nicholas Piggin 2018-04-04 23:57 ` Nicholas Piggin 2018-04-05 3:00 ` Dan Williams 2018-04-05 3:00 ` Dan Williams 2018-04-05 5:04 ` Nicholas Piggin 2018-04-05 5:04 ` Nicholas Piggin 2018-04-05 5:53 ` Balbir Singh 2018-04-05 5:53 ` Balbir Singh 2018-04-05 6:45 ` Nicholas Piggin 2018-04-05 6:45 ` Nicholas Piggin 2018-04-05 15:00 ` Dan Williams 2018-04-05 15:00 ` Dan Williams 2018-05-01 20:57 ` Dan Williams [this message] 2018-05-01 20:57 ` Dan Williams 2018-05-02 12:36 ` Balbir Singh 2018-05-02 12:36 ` Balbir Singh 2018-04-05 20:40 ` Jeff Moyer 2018-04-05 20:40 ` Jeff Moyer 2018-04-06 1:26 ` Nicholas Piggin 2018-04-06 1:26 ` Nicholas Piggin 2018-04-06 9:25 ` Balbir Singh 2018-04-06 9:25 ` Balbir Singh 2018-04-06 15:46 ` Luck, Tony 2018-04-06 15:46 ` Luck, Tony 2018-04-04 23:19 ` [RESEND 3/3] powerpc/mce: Handle memcpy_mcsafe Balbir Singh 2018-04-04 23:19 ` Balbir Singh
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=CAPcyv4hwb5ebVpYvAn+Bof_NxO6T3X1K+0B7Xbd07FrK8xZi7Q@mail.gmail.com \ --to=dan.j.williams@intel.com \ --cc=hch@lst.de \ --cc=linux-nvdimm@lists.01.org \ --cc=linuxppc-dev@lists.ozlabs.org \ --cc=mawilcox@microsoft.com \ --cc=mpe@ellerman.id.au \ --cc=npiggin@gmail.com \ --cc=tony.luck@intel.com \ /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: linkBe 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.