linux.git/net/ceph/osdmap.c, branch v6.6

libceph: print fsid and epoch with osd id

2022-08-02T22:54:12+00:00

Print fsid and epoch in libceph log messages to distinct from which
each message come.

[ idryomov: don't bother with gid for now, print epoch instead ]

Signed-off-by: Satoru Takeuchi 
Signed-off-by: Daichi Mukai 
Reviewed-by: Ilya Dryomov 
Signed-off-by: Ilya Dryomov

libceph: check pointer before assigned to "c->rules[]"

2022-08-02T22:54:12+00:00

It should be better to check pointer firstly, then assign it
to c->rules[]. Refine code a little bit.

Signed-off-by: Li Qiong 
Reviewed-by: Ilya Dryomov 
Signed-off-by: Ilya Dryomov

mm: allow !GFP_KERNEL allocations for kvmalloc

2022-01-15T14:30:29+00:00

Support for GFP_NO{FS,IO} and __GFP_NOFAIL has been implemented by
previous patches so we can allow the support for kvmalloc.  This will
allow some external users to simplify or completely remove their
helpers.

GFP_NOWAIT semantic hasn't been supported so far but it hasn't been
explicitly documented so let's add a note about that.

ceph_kvmalloc is the first helper to be dropped and changed to kvmalloc.

Link: https://lkml.kernel.org/r/20211122153233.9924-5-mhocko@kernel.org
Signed-off-by: Michal Hocko 
Reviewed-by: Uladzislau Rezki (Sony) 
Acked-by: Vlastimil Babka 
Cc: Christoph Hellwig 
Cc: Dave Chinner 
Cc: Ilya Dryomov 
Cc: Jeff Layton 
Cc: Neil Brown 
Cc: Sebastian Andrzej Siewior 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

libceph: Fix spelling mistakes

2021-06-03T20:24:23+00:00

Fix some spelling mistakes in comments:
enconding  ==> encoding
ambigous  ==> ambiguous
orignal  ==> original
encyption  ==> encryption

Signed-off-by: Zheng Yongjun 
Signed-off-by: David S. Miller

net: ceph: Fix a typo in osdmap.c

2021-03-26T00:05:07+00:00

Modify "inital" to "initial" in net/ceph/osdmap.c.

Reported-by: Hulk Robot 
Signed-off-by: Lu Wei 
Signed-off-by: David S. Miller

libceph, ceph: get and handle cluster maps with addrvecs

2020-12-14T22:21:50+00:00

In preparation for msgr2, make the cluster send us maps with addrvecs
including both LEGACY and MSGR2 addrs instead of a single LEGACY addr.
This means advertising support for SERVER_NAUTILUS and also some older
features: SERVER_MIMIC, MONENC and MONNAMES.

MONNAMES and MONENC are actually pre-argonaut, we just never updated
ceph_monmap_decode() for them.  Decoding is unconditional, see commit
23c625ce3065 ("libceph: assume argonaut on the server side").

SERVER_MIMIC doesn't bear any meaning for the kernel client.

Since ceph_decode_entity_addrvec() is guarded by encoding version
checks (and in msgr2 case it is guarded implicitly by the fact that
server is speaking msgr2), we assume MSG_ADDR2 for it.

Signed-off-by: Ilya Dryomov

libceph: multiple workspaces for CRUSH computations

2020-10-12T13:29:26+00:00

Replace a global map->crush_workspace (protected by a global mutex)
with a list of workspaces, up to the number of CPUs + 1.

This is based on a patch from Robin Geuze .
Robin and his team have observed a 10-20% increase in IOPS on all
queue depths and lower CPU usage as well on a high-end all-NVMe
100GbE cluster.

Signed-off-by: Ilya Dryomov

libceph: support for balanced and localized reads

2020-06-01T11:22:53+00:00

OSD-side issues with reads from replica have been resolved in
Octopus.  Reading from replica should be safe wrt. unstable or
uncommitted state now, so add support for balanced and localized
reads.

There are two cases when a read from replica can't be served:

- OSD may silently drop the request, expecting the client to
  notice that the acting set has changed and resend via the usual
  means (handled with t->used_replica)

- OSD may return EAGAIN, expecting the client to resend to the
  primary, ignoring replica read flags (see handle_reply())

Signed-off-by: Ilya Dryomov 
Reviewed-by: Jeff Layton

libceph: crush_location infrastructure

2020-06-01T11:22:53+00:00

Allow expressing client's location in terms of CRUSH hierarchy as
a set of (bucket type name, bucket name) pairs.  The userspace syntax
"crush_location = key1=value1 key2=value2" is incompatible with mount
options and needed adaptation.  Key-value pairs are separated by '|'
and we use ':' instead of '=' to separate keys from values.  So for:

  crush_location = host=foo rack=bar

one would write:

  crush_location=host:foo|rack:bar

As in userspace, "multipath" locations are supported, so indicating
locality for parallel hierarchies is possible:

  crush_location=rack:foo1|rack:foo2|datacenter:bar

Signed-off-by: Ilya Dryomov 
Reviewed-by: Jeff Layton

libceph: decode CRUSH device/bucket types and names

2020-06-01T11:22:53+00:00

These would be matched with the provided client location to calculate
the locality value.

Signed-off-by: Ilya Dryomov 
Reviewed-by: Jeff Layton