On Wed, May 30, 2018 at 8:50 PM, Jeff Layton <jlayton@xxxxxxxxxx> wrote:
> On Wed, 2018-05-30 at 19:43 +0200, Ilya Dryomov wrote:
>> The intent behind making it a per-request setting was that it would be
>> set for writes, but not for reads. As it is, the flag is set for all
>> fs/ceph requests except for pool perm check stat request (technically
>> a read).
>>
>> ceph_osdc_abort_on_full() skips reads since the previous commit and
>> I don't see a use case for marking individual requests.
>>
>> Signed-off-by: Ilya Dryomov <idryomov@xxxxxxxxx>
>
> I'm assuming that it's not possible for (e.g.) an RBD and CephFS client
> to share an osdc? We'd almost certainly want different semantics in
> those two cases, I'd think.
>
> Looking at the code, it seems like it's not possible for now. If we
> think that might be something to pursue in the future, then we may need
> to rethink this.
No, it is not and has never been possible.
Thanks,
Ilya
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
