Remove unused support for SysV shared memory

src/trusted/desc/linux/nacl_desc_sysv_shm.h

Index: src/trusted/desc/linux/nacl_desc_sysv_shm.h
diff --git a/src/trusted/desc/linux/nacl_desc_sysv_shm.h b/src/trusted/desc/linux/nacl_desc_sysv_shm.h
deleted file mode 100644
index 3ac48a32bd0b3e08d92f3051b9cc727acf3deddf..0000000000000000000000000000000000000000
--- a/src/trusted/desc/linux/nacl_desc_sysv_shm.h
+++ /dev/null
@@ -1,74 +0,0 @@
-/*
- * Copyright (c) 2011 The Native Client Authors. All rights reserved.
- * Use of this source code is governed by a BSD-style license that can be
- * found in the LICENSE file.
- */
-
-/*
- * NaCl service runtime.  Transferrable shared memory objects.
- */
-#ifndef NATIVE_CLIENT_SRC_TRUSTED_DESC_NACL_DESC_LINUX_SYSV_SHM_H_
-#define NATIVE_CLIENT_SRC_TRUSTED_DESC_NACL_DESC_LINUX_SYSV_SHM_H_
-
-#include "native_client/src/include/portability.h"
-#include "native_client/src/include/nacl_base.h"
-
-#include "native_client/src/trusted/desc/nacl_desc_base.h"
-
-EXTERN_C_BEGIN
-
-struct NaClDescEffector;
-struct NaClDescXferState;
-struct NaClMessageHeader;
-struct nacl_abi_stat;
-
-/*
- * Since the SysV shared memory abstraction does not permit mapping in
- * only a portion of the shared memory object (offset==0), the SysV
- * shm objects have their own fstat object type.  The user code should
- * not encounter SysV shm objects normally and is unable to create any
- * SysV shm objects; the only source of SysV shm objects is in the
- * context of Pepper2d, and the Pepper2d library code should hide
- * this implementation detail.
- */
-extern struct NaClDescVtbl const kNaClDescSysvShmVtbl;
-
-/*
- * SysV shared memory objects have weird semantics.  There is no way
- * for untrusted code to create one.  These are normally imported --
- * from the GPU process when we are embedded in Chrome -- and the shm
- * object is externally owned, and we do not have to worry about its
- * lifetime.  The normal Ctor is here primarily for completeness.
- * Note, however, the following semantics: the process that Ctor'd the
- * SysV shm object is the owner; the SysV shm object may be
- * externalized (its ID sent) and internalized in another process;
- * however, there is no sharing of ownership nor reference counting --
- * the receiving process can access the SysV shm object as long as it
- * is live, but when the owner Dtors its object, the ID will get
- * invalidated, and the receiving process's accesses will fail.  The
- * RMID only occurs in the Dtor of the owner, not in the processes
- * that internalized the SysV shm object in a nrd xfer.
- */
-struct NaClDescSysvShm {
-  struct NaClDesc           base NACL_IS_REFCOUNT_SUBCLASS;
-  int                       id;
-  size_t                    size;
-  int                       rmid_in_dtor;
-};
-
-int NaClDescSysvShmInternalize(struct NaClDesc               **baseptr,
-                               struct NaClDescXferState      *xfer,
-                               struct NaClDescQuotaInterface *quota_interface)
-    NACL_WUR;
-
-
-int NaClDescSysvShmImportCtor(struct NaClDescSysvShm  *self,
-                              int                     id,
-                              nacl_off64_t            size) NACL_WUR;
-
-int NaClDescSysvShmCtor(struct NaClDescSysvShm  *self,
-                        nacl_off64_t            size) NACL_WUR;
-
-EXTERN_C_END
-
-#endif  /* NATIVE_CLIENT_SRC_TRUSTED_DESC_LINUX_NACL_DESC_SYSV_SHM_H_ */