[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150610073316.GB3369@lst.de>
Date: Wed, 10 Jun 2015 09:33:16 +0200
From: Christoph Hellwig <hch@....de>
To: Dan Williams <dan.j.williams@...el.com>
Cc: Christoph Hellwig <hch@....de>,
"linux-nvdimm@...ts.01.org" <linux-nvdimm@...ts.01.org>,
Jens Axboe <axboe@...nel.dk>,
Stephen Rothwell <sfr@...b.auug.org.au>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Neil Brown <neilb@...e.de>,
Greg KH <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Linux ACPI <linux-acpi@...r.kernel.org>,
jmoyer <jmoyer@...hat.com>, linux-api@...r.kernel.org,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v5 05/21] libnvdimm: control (ioctl) messages for
libnvdimm bus and dimm devices
On Mon, Jun 08, 2015 at 11:57:42PM -0700, Dan Williams wrote:
> Data payload size for one, these commands transfer more than a page
> worth of data at a time.
>
> Even if we killed the ioctl interface to userspace we still need all
> the ugly data marshaling code in the kernel to craft properly
> formatted ACPI _DSM messages. I try to share as much common
> infrastructure from the ACPI _DSM implementation to the ioctl
> interface (nd_cmd_dimm_desc() + nd_cmd_bus_desc()).
Ok. Not a fan of these dual interfaces but in this case they might be
justified.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists