learn linux and unix commands - unix shell scripting

Presenting risk

03-16-2009

Registered User

26,240, 27

Join Date: Sep 2000

Last Activity: 1 August 2008, 3:09 PM EDT

Posts: 26,240

Thanks Given: 0

Thanked 27 Times in 26 Posts

Presenting risk

We talk about risk, risk assessment, risk analysis, and risk management. A lot. But people are remarkably bad at really understanding risks.

This web page and animation on understanding uncertainty was created to address medical risks. However, it points out a number of ways that we can either misrepresent, or misunderstand, risk in general.

More...

Linux Bot

View Public Profile for Linux Bot

Find all posts by Linux Bot

Previous Thread | Next Thread

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Presenting current LUNs to new OS. RHEL 7, LVM

All, We have a physical server (Lenovo 3950) that we need to upgrade the OS from RHEL 6 to RHEL 7. We do not want to do an in-place upgrade but rather start with a fresh OS install. The plan is to remove the two local drives (Raid 1) and install two new drives for the fresh RHEL 7 install. ...

2. UNIX for Beginners Questions & Answers

Presenting data in column format

I have written a script that that takes file names and breaks them apart. File names are : aal_mock.war.deployed AuroralMockService-1.0.war.deployed consumerProfile.war.deployed EbillMock.war.deployed IAMAOGServices.war.deployed IAMPermission.war.deployed...

3. Shell Programming and Scripting

Presenting the user a menu in Bash ...

Hello, I am trying to write a bash script function to present the user a menu of options. The following is what I have so far: function MainMenu { while ] do echo "--------------------------------------------------------------------------------" echo...

LEARN ABOUT SUSE

blk_make_request

BLK_MAKE_REQUEST(9)						   Block Devices					       BLK_MAKE_REQUEST(9)

NAME

       blk_make_request - given a bio, allocate a corresponding struct request.

SYNOPSIS

       struct request * blk_make_request(struct request_queue * q, struct bio * bio, gfp_t gfp_mask);

ARGUMENTS

       q
	   target request queue

       bio
	   The bio describing the memory mappings that will be submitted for IO. It may be a chained-bio properly constructed by block/bio layer.

       gfp_mask
	   gfp flags to be used for memory allocation

DESCRIPTION

       blk_make_request is the parallel of generic_make_request for BLOCK_PC type commands. Where the struct request needs to be farther
       initialized by the caller. It is passed a struct bio, which describes the memory info of the I/O transfer.

       The caller of blk_make_request must make sure that bi_io_vec are set to describe the memory buffers. That bio_data_dir will return the
       needed direction of the request. (And all bio's in the passed bio-chain are properly set accordingly)

       If called under none-sleepable conditions, mapped bio buffers must not need bouncing, by calling the appropriate masked or flagged
       allocator, suitable for the target device. Otherwise the call to blk_queue_bounce will BUG.

WARNING

       When allocating/cloning a bio-chain, careful consideration should be given to how you allocate bios. In particular, you cannot use
       __GFP_WAIT for anything but the first bio in the chain. Otherwise you risk waiting for IO completion of a bio that hasn't been submitted
       yet, thus resulting in a deadlock. Alternatively bios should be allocated using bio_kmalloc instead of bio_alloc, as that avoids the
       mempool deadlock. If possible a big IO should be split into smaller parts when allocation fails. Partial allocation should not be an error,
       or you risk a live-lock.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						       BLK_MAKE_REQUEST(9)