Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

ksize(9) [centos man page]

KSIZE(9)						    Memory Management in Linux							  KSIZE(9)

ksize - get the actual amount of memory allocated for a given object SYNOPSIS
size_t ksize(const void * objp); ARGUMENTS
objp Pointer to the object DESCRIPTION
kmalloc may internally round up allocations and return more memory than requested. ksize can be used to determine the actual amount of memory allocated. The caller may use this additional memory, even though a smaller amount of memory was initially specified with the kmalloc call. The caller must guarantee that objp points to a valid object previously allocated with either kmalloc or kmem_cache_alloc. The object must not be freed during the duration of the call. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 KSIZE(9)

Check Out this Related Man Page

BIO_ALLOC_BIOSET(9)						   The Linux VFS					       BIO_ALLOC_BIOSET(9)

bio_alloc_bioset - allocate a bio for I/O SYNOPSIS
struct bio * bio_alloc_bioset(gfp_t gfp_mask, int nr_iovecs, struct bio_set * bs); ARGUMENTS
gfp_mask the GFP_ mask given to the slab allocator nr_iovecs number of iovecs to pre-allocate bs the bio_set to allocate from. DESCRIPTION
If bs is NULL, uses kmalloc to allocate the bio; else the allocation is backed by the bs's mempool. When bs is not NULL, if __GFP_WAIT is set then bio_alloc will always be able to allocate a bio. This is due to the mempool guarantees. To make this work, callers must never allocate more than 1 bio at a time from this pool. Callers that need to allocate more than 1 bio must always submit the previously allocated bio for IO before attempting to allocate a new one. Failure to do so can cause deadlocks under memory pressure. Note that when running under generic_make_request (i.e. any block driver), bios are not submitted until after you return - see the code in generic_make_request that converts recursion into iteration, to prevent stack overflows. This would normally mean allocating multiple bios under generic_make_request would be susceptible to deadlocks, but we have deadlock avoidance code that resubmits any blocked bios from a rescuer thread. However, we do not guarantee forward progress for allocations from other mempools. Doing multiple allocations from the same mempool under generic_make_request should be avoided - instead, use bio_set's front_pad for per bio allocations. RETURNS
Pointer to new bio on success, NULL on failure. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 BIO_ALLOC_BIOSET(9)
Man Page

9 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Tar: tape blocksize error

When trying to extract a tar file in HP-UX using tar -xvf command it exits with the following error :"Tar: tape blocksize error". Tar file is created using the following command with MKS toolkit(Unix Simulation Kit for Windows env) under Windows 2000 Professional: "$tar -cvf test.tar test.txt... (1 Reply)
Discussion started by: ramkumar
1 Replies

2. UNIX for Dummies Questions & Answers

Blocksize problem restoring file from tape

I was recently given the responsibility of the unix box at our work. Without much training, I now have to go back and restore a file from tape. I'm having some trouble with it. I'm getting an error with the blocksize. The part of the script that does the tar looks like this: tar cvfX... (11 Replies)
Discussion started by: citrowske
11 Replies

3. UNIX for Dummies Questions & Answers

How to change blocksize for in tar command

How can I change the blocksize in tar command? tar cvf test.tar a 1K If we need to set the blocksize to 20, how to do that? Please advise. Thank you. (10 Replies)
Discussion started by: KhawHL
10 Replies

4. UNIX for Advanced & Expert Users

tar: tape blocksize error

Hi, I have tar: tape blocksize error when launching # gunzip < TierDB.tar.gz |tar -xvf /data/ora/DREC tar: tape blocksize error Can you please help me ? It is urgent. Many thanks. (1 Reply)
Discussion started by: big123456
1 Replies

5. UNIX for Dummies Questions & Answers

tar: blocksize

Hi, When doing tar -xvf to untar, some tar versions display the blocksize: “tar: blocksize = 6” my goal is to avoid this message. One way of doing it is to specify the blocksize: tar -xvfb <tar_file> 6 Is there a setting in tar or a tar version to avoid this type of message without... (0 Replies)
Discussion started by: melanie_pfefer
0 Replies

6. UNIX for Dummies Questions & Answers

tar: blocksize = 0 - Error message?

Hi All, While viewing tar file using "tar tf file.tar" command, I have received "tar: blocksize = 0" message and while extracting a particular file from the same tar file (file.tar) I have received the same message and nothing is extracted. Above commands ran in a shell script so, I... (3 Replies)
Discussion started by: Tlogine
3 Replies

7. Solaris

Tar blockSize problem

Hi, i have got a tar file some 200MB big and i have ftp'ed the tar file over from one server to another but it does not seem to extract. its giving the following message: tar xvf saptar tar: blocksize = 2 Its the first time i used tar so I not got any ideas why its giving this message?... (2 Replies)
Discussion started by: scriptingmani
2 Replies

8. Linux

Linux Thread Stack Size pthread_attr_setstacksize

I have MultiThreaded Application in Linux. I am Setting the stack size using pthread_attr_setstacksize. The stack size i set is greter than PTHREAD_STACK_MIN i.e. 16384 bytes for my system. i am setting the stack size to 17408 bytes, and my application crashes due to insufficient stack size.... (1 Reply)
Discussion started by: Kedar Sabnis
1 Replies

9. Solaris

Limit: stacksize: Can't remove limit

Hi all, I'm using to Solaris machine. When I run a simple script this messenger come out:"limit: stacksize: Can't remove limit". Any one know the way to resolve this problem without reboot the machine? Thanks in advance. (3 Replies)
Discussion started by: Diabolist9
3 Replies

Featured Tech Videos