zeroshade commented on code in PR #34972: URL: https://github.com/apache/arrow/pull/34972#discussion_r1204346824
########## docs/source/format/CDeviceDataInterface.rst: ########## @@ -0,0 +1,613 @@ +.. Licensed to the Apache Software Foundation (ASF) under one +.. or more contributor license agreements. See the NOTICE file +.. distributed with this work for additional information +.. regarding copyright ownership. The ASF licenses this file +.. to you under the Apache License, Version 2.0 (the +.. "License"); you may not use this file except in compliance +.. with the License. You may obtain a copy of the License at + +.. http://www.apache.org/licenses/LICENSE-2.0 + +.. Unless required by applicable law or agreed to in writing, +.. software distributed under the License is distributed on an +.. "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +.. KIND, either express or implied. See the License for the +.. specific language governing permissions and limitations +.. under the License. + +.. highlight:: c + +.. _c-device-data-interface: + +================================= +The Arrow C Device data interface +================================= + +.. note:: The Arrow C Device Data Interface should be considered experimental + +Rationale +========= + +The current :ref:`C Data Interface <c-data-interface>`, and most +implementations of it, make the assumption that all data buffers provided +are CPU buffers. Since Apache Arrow is designed to be a universal in-memory +format for representing tabular ("columnar") data, there will be the desire +to leverage this data on Non-CPU hardware such as GPUs. One example of such +a case is the `RAPIDS cuDF library` which uses the Arrow memory format with Review Comment: sorry, not `:ref:`, but adding the `_` to indicate it. I'm still more used to md than rst lol -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
