search for: ip_mrt_cache

...sgpool-64 44 44 1024 4 1 sgpool-32 48 48 512 8 1 sgpool-16 75 75 256 15 1 sgpool-8 153 210 128 30 1 scsi_io_context 0 0 104 37 1 UNIX 377 399 512 7 1 ip_mrt_cache 0 0 128 30 1 tcp_bind_bucket 14 203 16 203 1 inet_peer_cache 81 118 64 59 1 secpath_cache 0 0 128 30 1 xfrm_dst_cache 0 0 384 10 1 ip_dst_cache 176 240 256 15 1 arp_cache...

...40 40 192 20 scsi_io_context 0 0 104 37 rpc_buffers 8 8 2048 2 rpc_tasks 8 20 192 20 rpc_inode_cache 0 0 448 9 UNIX 42 50 384 10 ip_mrt_cache 0 0 128 30 tcp_bind_bucket 49 203 16 203 inet_peer_cache 1 59 64 59 secpath_cache 0 0 128 30 xfrm_dst_cache 0 0 320 12 ip_dst_cache 15 30 256...

Hi Guys, My users are reporting some issues with memory on our lustre 1.8.1 clients. It looks like when they submit a single job at a time the run time was about 4.5 minutes. However, when they ran multiple jobs (10 or less) on a client with 192GB of memory on a single node the run time for each job was exceeding 3-4X the run time for the single process. They also noticed that the swap space