Search Options

Results per page
Sort
Preferred Languages
Advance

Results 1 - 4 of 4 for inmemory (0.04 sec)

  1. cmd/erasure-server-pool-rebalance.go

    	if err != nil && !errors.Is(err, errConfigNotFound) {
    		return err
    	}
    
    	z.rebalMu.Lock()
    	defer z.rebalMu.Unlock()
    
    	// if not found, we store the memory metadata back
    	// when rebalance status changed, will notify all nodes update status to memory, we can treat the memory metadata is the latest status
    	if errors.Is(err, errConfigNotFound) {
    		r = z.rebalMeta
    	}
    
    	switch opts {
    	case rebalSaveStoppedAt:
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Thu Sep 04 20:47:24 UTC 2025
    - 28.9K bytes
    - Viewed (0)
  2. src/cmd/asm/internal/asm/testdata/loong64enc1.s

    	ADDV16	$(8<<16), R4, R5	// ADDV16	$524288, R4, R5		// 85200010
    	ADDV16	$(32767<<16), R4, R5	// ADDV16	$2147418112, R4, R5	// 85fcff11
    	ADDV16	$(16<<16), R4		// ADDV16	$1048576, R4		// 84400010
    
    	// Loong64 atomic memory access instructions
    	AMSWAPB		R14, (R13), R12 // ac395c38
    	AMSWAPH		R14, (R13), R12 // acb95c38
    	AMSWAPW		R14, (R13), R12 // ac396038
    	AMSWAPV		R14, (R13), R12 // acb96038
    	AMCASB		R14, (R13), R12 // ac395838
    Registered: Tue Sep 09 11:13:09 UTC 2025
    - Last Modified: Thu Sep 04 19:24:25 UTC 2025
    - 35.5K bytes
    - Viewed (0)
  3. cmd/erasure-object.go

    		// Release lock when the metadata is verified, and reader
    		// is ready to be read.
    		//
    		// This is possible to be lock free because
    		// - xl.meta for inlined objects has already read the data
    		//   into memory, any mutation on xl.meta subsequently is
    		//   inconsequential to the overall read operation.
    		// - xl.meta metadata is still verified for quorum under lock()
    		//   however writing the response doesn't need to serialize
    Registered: Sun Sep 07 19:28:11 UTC 2025
    - Last Modified: Sun Sep 07 16:13:09 UTC 2025
    - 80.4K bytes
    - Viewed (0)
  4. docs/en/docs/release-notes.md

        * This was reported internally by [@rushilsrivastava](https://github.com/rushilsrivastava) as a memory leak when the server had unhandled exceptions that would produce internal server errors, the memory allocated before that point would not be released.
    Registered: Sun Sep 07 07:19:17 UTC 2025
    - Last Modified: Fri Sep 05 12:48:45 UTC 2025
    - 544.1K bytes
    - Viewed (0)
Back to top