[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AT5PR8401MB1169FF6CBFDD789452E9CB17ABBF0@AT5PR8401MB1169.NAMPRD84.PROD.OUTLOOK.COM>
Date: Thu, 20 Dec 2018 16:08:39 +0000
From: "Elliott, Robert (Persistent Memory)" <elliott@....com>
To: "dgilbert@...erlog.com" <dgilbert@...erlog.com>,
Christoph Hellwig <hch@....de>,
Boaz Harrosh <ooo@...ctrozaur.com>
CC: "axboe@...nel.dk" <axboe@...nel.dk>,
"martin.petersen@...cle.com" <martin.petersen@...cle.com>,
Johannes Thumshirn <jthumshirn@...e.de>,
Benjamin Block <bblock@...ux.vnet.ibm.com>,
"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
"linux-block@...r.kernel.org" <linux-block@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: remove exofs, the T10 OSD code and block/scsi bidi support V3
> -----Original Message-----
> From: linux-kernel-owner@...r.kernel.org <linux-kernel-
> owner@...r.kernel.org> On Behalf Of Douglas Gilbert
> Sent: Wednesday, December 19, 2018 9:02 PM
> Subject: Re: remove exofs, the T10 OSD code and block/scsi bidi support V3
>
...
> While on the subject of bidi, the order of transfers: is the data-out
> (to the target) always before the data-in or is it the target device
> that decides (depending on the semantics of the command) who is first?
In SCSI, that was command-specific. Some necessitated intermixing the
transfers, while others did all one direction before all the other
direction.
---
Robert Elliott, HPE Persistent Memory
Powered by blists - more mailing lists