text:
Simply Effective, Beautifully Compact
Powerful UVC sanitation kills over 60 disease causing microorganisms and pathogens without the use of harmful chemicals. Our sanitizing chamber is housed inside the spa's control box and continuously sanitizes water that passes through the chamber. Since you will never come in contact with the UVC light, this setting can be turned on while you are enjoying your spa.
To greatly improve heating performance, we use 2200W PTC heater in the mid to high end range. This heater is not only stronger but also smarter. It can intelligently allocate its power according to the functions that are being activated. When only activate the heater it will run at its full power of 2200W. When the bubble or jet function is on, it will run at a lower power. So even when enjoy the dynamic massage, the water never gets cold.
Item Number
Size and Weight
Height: 70 cm (28″)
Width: 204 cm (80″)
Net Weight: 42.5 kg (93.7 lb)
Filled Weight: 972.5 kg (2,144 lb)
Wired Controller
Hydro Jets
Variable Speed Bubbles
Heat Tech
Energy Saving Timer
Anti-icing System
Smart Filtration
UVC Sanitizer
O₃ Generator
Antibacterial Fabric
Child Safety Lock
Up to 6 adults
Water Capacity
Filled to the Max. Water Line
930 Liters (245 Gallons)
Control System: 220 – 240v / 50 Hz
Heater: 2200W
Massage Air Jet: 720W – 3 levels (300W, 500W, 720W)
Jet Pump: 225W
Hydro Massage System
Air Bubbling System: 138 Jets
Hydro Jets: 3 sets (6 adjustable hydro jets)
Heat Increasing Rate: 1.5 – 2.0°C per hour
Max. Water Temperature: 40°C (104°F)
Filter Pump
Circulated Water Flow: 1800 Liters (545 Gallons) per hour
Integrated Generator: 5.5W
Ozone Output: 30 – 50Mg/Hr
UKCA / CE approved
Colour Paper Box
85 x 61 x 62 cm
In the Box
Carlton Spa
Spa Cover
Inflatable Bladder
Filter Cartridge x 2
Filter Cartridge Base
Item Number
Size and Weight
Height: 70 cm (28″)
Width: 204 cm (80″)
Net Weight: 42.5 kg (93.7 lb)
Filled Weight: 972.5 kg (2,144 lb)
Wired Controller
Hydro Jets
Variable Speed Bubbles
Heat Tech
Energy Saving Timer
Anti-icing System
Smart Filtration
UVC Sanitizer
O₃ Generator
Antibacterial Fabric
Child Safety Lock
Up to 6 adults
Water Capacity
Filled to the Max. Water Line
930 Liters (245 Gallons)
Control System: 220 – 240v / 50 Hz
Heater: 2200W
Massage Air Jet: 720W – 3 levels (300W, 500W, 720W)
Jet Pump: 225W
Hydro Massage System
Air Bubbling System: 138 Jets
Hydro Jets: 3 sets (6 adjustable hydro jets)
Heat Increasing Rate: 1.5 – 2.0°C per hour
Max. Water Temperature: 40°C (104°F)
Filter Pump
Circulated Water Flow: 1800 Liters (545 Gallons) per hour
Integrated Generator: 5.5W
Ozone Output: 30 – 50Mg/Hr
SAA / RTM approved
Colour Paper Box
85 x 61 x 62 cm
In the Box
Carlton Spa
Spa Cover
Inflatable Bladder
Filter Cartridge x 2
Filter Cartridge Base
Item Number
Size and Weight
Height: 28″ (70 cm)
Width: 71″ (180 cm)
Net Weight: 80.5 lb (36.5 kg)
Filled Weight: 1,623.7 lb (736.5 kg)
Wired Controller
Hydro Jets
Variable Speed Bubbles
Heat Tech
Energy Saving Timer
Anti-icing System
Smart Filtration
UVC Sanitizer
O₃ Generator
Antibacterial Fabric
Child Safety Lock
Up to 4 adults
Water Capacity
Filled to the Max. Water Line
184 Gallons (700 Litres)
Control System: 110 – 120v / 60 Hz
Heater: 1350W
Massage Air Jet: 700W – 3 levels (300W, 450W, 700W)
Jet Pump: 195W
Hydro Massage System
Air Bubbling System: 118 Jets
Hydro Jets: 2 Sets (4 high efficiency hydro jets)
Heat Increasing Rate: 2.5 – 3.5°F per hour
Max. Water Temperature: 104°F (40°F)
Filter Pump
Circulated Water Flow: 545 Gallons (1800 L) per hour
Integrated Generator: 5.5W
Ozone Output: 30 – 50Mg/Hr
ETL approved
Colour Paper Box
28.3″ x 22.8″ x 25.2″
In the Box
Carlton Spa
Spa Cover
Inflatable Bladder
Filter Cartridge x 2
Filter Cartridge Base
No products were found matching your selection.
Copyright 2024 MSpa | All Rights Reserved
Dear users:
Oriental Recreational Products (Shanghai) Co., Ltd. (hereinafter referred to as "ORPC", "we" and "our") provides various technical and management support. ORPC knows the importance of privacy to you and will respect your privacy. This Personal Data Protection Statement (hereinafter referred to as the "Statement") will explain how ORPC uses and protects your personal data and privacy when you participate in MSPA. Please read it carefully.
This Statement shall not cover all possible situations of personal data processing, and the statement related to personal data processing in specific scenarios shall be provided by ORPC before supplementing statements or collecting personal data.
We made this statement to help you know the following:
1. How we collect and use your personal data.
2. Cache and similar technologies
3. How we disclose the personal data.
4. How we access and control your personal data.
5. How we protect and keep your personal data.
6. How we process children's personal data
7. Third-party providers and their services
8. How to transfer your personal data internationally
9. How to update this Statement.
10. How to contact us.
1. How we collect and use your personal data.
Personal data refers to the information that can identify a specific individual when used alone or in combination with other information. After you read and agree to this statement, your personal data will be collected when you use our products or services, so as to provide you with high-quality weather services and product information. The following details the scenarios in which we process your personal data, the types, methods and purposes of personal data involved.
1.1When you register for MSPA, we will send a verification code to your email address to confirm the validity of your registration and delete your email records within 30 minutes of your registration.
1.2 When you open MSPA application, we will provide weather information of your city through the IP address of your network.
2. Cache and similar technologies
2.1 cache
To ensure that our applications work properly, we sometimes place a small piece of data on your mobile device, which is called cache. Cache is a text file stored on a computer or mobile device by the server. The contents of the cache can only be retrieved or read by the server that created the cache. The text in the cache usually consists of an identifier, a site name, and some numbers and characters. Cache is unique to the application you use, enabling the application to store data such as your preferences or items in the shopping cart.
Like many other IoT service providers, ORPC uses cache to improve user experience. The session cache is deleted after each access, while the persistent cache remains after multiple accesses. Cache allows the application to remember your settings, such as language, the default control state of the product, or other preferences. This means that users do not need to reset preferences every time they access. On the contrary, if you do not use the cache, the application will treat you as a new visitor every time it loads a page. ORPC will not use the cache for any purpose other than the purpose stated in this statement. You can manage or delete the cache according to your preferences. You can clear all caches stored on the device.
3. How we disclose the personal data.
Unless otherwise specified in this Statement or applicable laws, ORPC will not disclose your personal data to third parties other than affiliated or subsidiary companies of ORPC through sale, lease, transaction or other forms without your express consent. When we have legitimate reasons to believe that it is necessary to access, disclose and retain your personal data for the following purposes, we may access, disclose and retain your personal data as permitted by law:
3.1 Complying with applicable laws or responding to the effective legal procedures of law enforcement or other government agencies;
3.2 Ensuring the security and availability of ORPC's information and communication system, avoiding spam mail or fraud, or preventing serious physical injury or loss of life, or preventing or protecting ORPC's computer or network from any attack;
3.3 Protecting ORPC's intellectual property, information assets and other assets and rights;
3.4 In addition, as a global company, we may share personal data with the affiliated or subsidiary companies of ORPC. Only necessary data will be disclosed.
4. How we access and control your personal data.
It is your responsibility to ensure that all personal data submitted to ORPC is correct. ORPC is committed to maintaining the accuracy and completeness of personal data and updating personal data in a timely manner.
To the extent required by applicable law, you shall:
4.1 Have the right to access the personal data you provide to us about you;
4.2 Ask us to update or correct the inaccuracies in the data;
4.3 Object to or restrict our use of your personal data;
4.4 Require us to delete your personal data from our database.
To exercise these rights, please write to email@example.com. If we have reasonable grounds to believe that the request is fraudulent, unfeasible, or likely to endanger the privacy of others, we may reject the request.
When ORPC processes your personal data according to your consent, you have the right to withdraw your consent at any time when permitted by applicable law. However, the withdrawal does not affect the legality and validity of our processing of your personal data based on your consent prior to the withdrawal, nor does it affect our processing of your personal data based on reasons other than your consent.
ORPC will not delay the deletion of personal data for no reason when it no longer needs the personal data.
If you believe that the way we use to process your personal data does not comply with applicable data protection laws, you can contact the relevant data protection authority. You can obtain information on how to contact EU data protection authorities at:
5. How we protect and keep your personal data.
The security of your personal data is very important to us. We have taken and will continue to take reasonable and appropriate security measures to protect your personal data from unauthorized access, disclosure, use, damage or loss. For example, we use encryption to keep data confidential, protection mechanisms to prevent attacks, and access control mechanisms to allow only authorized access to your personal data. We also train employees on security and privacy protection to raise their awareness of personal data protection. ORPC shall not be liable for any unauthorized access, disclosure, use, damage or loss of your personal data not caused by us. ORPC is committed to protecting your personal data. However, please note that no security measures can be perfect.
Your personal data will be stored on the server in the French Republic.
Unless otherwise provided or permitted by law, we will only retain your personal information for the time necessary for the purposes stated in this Statement. The data obtain by contacting you through email will be deleted within 7 natural days after the event. The personal data collected by filling in the questionnaire will be deleted within two years after the end of the activity. We will retain your registration information as long as your account is necessary to provide services to you. You can also choose to cancel your account. After you cancel your account, we will stop providing products and services based on this account, and delete the personal data you registered and submitted without special legal requirements. If the account is dormant for more than two years, we will stop providing products and services based on the account, and delete your personal data submitted for registration without special legal requirements.
When personal data leakage may cause high risks to the rights and freedoms of natural persons, ORPC will timely inform users of personal data leakage, even if the probability of occurrence is very little.
6. How we process children's personal data
This application is mainly for adults. Children cannot create an account without the consent of their parents or guardians. If the consent of parents is obtained in advance for the collection of personal data of children, we will only use or disclose such information where permitted by law and with the express consent of the child's parent or guardian, or where it is necessary to protect the child. If we accidentally collect the personal data of children without the prior confirmation and consent of their parents or guardians, we will stop the service and try to delete these data as soon as possible.
7. Third-party providers and their services
You may receive services from third parties instead of ORPC and its partners (hereinafter referred to as the "third parties").
Personal data storage services are provided by third parties, and ORPC has no control over such third parties. Nor can it control the privacy and data protection policies of third parties, and such third parties are not bound by this policy. Please refer to the privacy protection policies of these third parties before submitting personal information to third parties.
8. How to transfer your personal data across borders
As a global company, your personal data collected by ORPC shall be processed or accessed in countries/regions where you use our products and services, or where ORPC or its affiliates, subsidiaries, service providers or business partners exist. These jurisdictions may have different data protection laws.
In this case, ORPC will take measures to ensure that the data is processed in accordance with the requirements of this statement and applicable laws, including when the personal data of the data subject is transferred from the EU to a country or region whose data protection level has not been recognized by the European Commission. We may adopt various legal mechanisms, such as signing standard contract clauses approved by the European Commission, obtaining the consent of data subjects in the EU for cross-border transfers, and anonymizing personal data before cross-border transfers.
In this case, ORPC shall inform the controller of the legal requirement before processing, unless the law prohibits such information based on important reasons of public interest.
9. How to update this Statement.
ORPC reserves the right to update or change this Statement at any time. In case of any changes, we will post the latest privacy statement on this page. In case of material changes to this Privacy Statement, we may notify you through different channels.
10. How to contact us.
You can contact us at email@example.com .
Note: due to the differences in local laws, regulations and languages, this Statement may be inconsistent with this version. In case of any difference, the local language shall prevail.
Date of the latest revision: October 12, 2021
Oriental Recreational Products Co., Ltd. All rights reserved.
Software License and Service Agreement
Important notices
Oriental Recreational Products (Shanghai) Co., Ltd. (hereinafter referred to as "ORPC") hereby specially remind you (hereinafter referred to as the "users") of carefully reading and fully understanding this Software License and Service Agreement (hereinafter referred to as "this agreement"). The users shall carefully read and fully understanding all clauses of this agreement, especially those involving and exempting or limiting responsibilities of ORPC, dispute resolution and applicable laws. The clauses exempting or limiting responsibilities will be marked in bold, which shall be read with focus. Please read this agreement prudently, and choose whether to accept this agreement or not (the minors shall read accompanied by a legal guardian). In particular, your downloading, installation and use of ORPC software (hereinafter referred to as "this software") and acquiring and logging in account and other behaviors via this software will be deemed as your acceptance of this agreement, and your consent to be bound by all clauses of this agreement.
ORPC is entitled to revise this agreement independently, and the revised agreement clauses will be published on official website of ORPC (website: [www.the-mspa.com], hereinafter referred to as the "official website") or this software, and will come into effect upon the date of publication. The users can re-download and update installation of this software or check the latest version of the agreement clauses on the official website. After the agreement clauses are published, if the users don't accept the revised agreement clauses, please stop using this software and corresponding services immediately, and if the users continue to use this software and corresponding services after publication of the agreement clauses, it shall be deemed as their acceptance of the revised agreement clauses.
I. General provisions
In this privacy policy, some terms are defined as follows:
1.1. This agreement is concluded between the users and ORPC and its operation cooperator (hereinafter referred to as the "cooperator") regarding the users' downloading, installation and use of this software and corresponding services.
1.2. This software and corresponding services are provided by ORPC, to be installed on (including but not limited to) mobile intelligent terminal equipment, and ORPC will use this software to provide the users using such intelligent terminal with binding and operating intelligent products and other services.
1.3. Ownership and operation right to this software and corresponding services belong to ORPC.
II. Scope of software authorization
2.1. ORPC grants the users a personal, non-transferable, non-sub-licensable and non-exclusive use license of this software.
2.2. The users can download, install and use this software on single mobile terminal equipment for non-commercial purpose. But the users shall neither download, install and use this software for commercial operation purpose, nor replicate, change, modify, mount to run or create any derivative works of the data released from this software or during running process of this software to any terminal equipment, and interactive data between the client and the server during running process of this software, including but not limited to the forms of using plug-ins, access of plug-in or unauthorized third-party tools/services to this software, and if requiring commercial sales, replication and distribution, such as software preassembly and binding, written content from ORPC must be obtained.
2.3. Without express permission of ORPC, the users shall not install this software on other terminal equipment other than mobile intelligent terminal equipment, including but not limited to PC, set top box (STB), game machine, TV, DVD machine and so on.
2.4. The users can replicate this software for the purpose of using this software and corresponding services, and the act of replication should not exceed the purpose of backup. The backup copies must contain all copyright information contained in original data of this software.
2.5. Except the express scope of software authorization in this agreement, ORPC does not authorize any other right to the users, and if the users want to use other rights, they shall obtain written consent from ORPC separately.
III. Software downloading, installation and upgrading
3.1. The users shall download and install this software following the website or method designated by ORPC, and it is specially warned by ORPC that the users shall not download and install this software at non-designated website, so as to avoid the mobile intelligent terminal equipment from being infected with rogue programs that could damage the users' data and acquire the users' privacy information. If the users download this software or installation program having the same name with this software from third-parties not authorized by ORPC, ORPC can't guarantee normal use of this software, and the losses generated therefrom shall be assumed by the users independently.
3.2. The users must select software version compatible with the installed intelligent terminal equipment, otherwise, any software problem, equipment software or damage due to incompatibility between the software and equipment model shall be assumed by the users independently.
3.3. In order to improve experience of the users, and perfect the service contents, ORPC is entitled to either provide you with replacement, modification and upgrade services of this software from time to time, or charge expenses for the replacement, modification and upgrade, but ORPC will obtain your consent in advance regarding the charging matters. This software enables "upgrade prompt" function for the users by default, and the users can select to perform replacement, modification and upgrade of this software or not independently. After publication of replacement, modification and upgrade of this software, ORPC does not guarantee that the software not replaced, modified and upgraded can continue to be used or not, the users shall follow the official website to update and upgrade the software timely, so as to guarantee continued normal use of the equipment.
IV. Use specification
4.1. Under the condition of abiding by laws, regulations and this agreement, the users can use this software and corresponding services in accordance with this agreement, but the users shall not perform the following acts:
Delete all information on copyright in this software and other duplicates, and modify, delete or avoid the technical measures of this software set for protecting intellectual property right;
Perform reverse engineering of this software, such as disassembling, de-compilation or other means to try to obtain source code of this software;
By modifying or counterfeiting the instructions and data in software running, adding, deleting or changing the software functions or running effect, or using the software and method used for the above-mentioned purpose for operating or public communication, whether such acts are for commercial purpose or not;
Use this software to perform acts harming network security, including but not limited to: use unlicensed data or enter unlicensed server/account; enter public network or others' operating system without permission and delete, modify and add storage information; attempt to probe, scan and test this software's system or network vulnerabilities or perform other acts damaging network security; damage normal running of this software, spread vogue program or virus on purpose and perform other acts damaging and interfering with normal network information service; counterfeit name or partial name of TCP/IP data package;
By using third-party compatible software and system not developed, authorized or recognized by ORPC, the users log in or use this software and corresponding services, or produce, publish and spread the above-mentioned tools;
Without written consent of ORPC, the users implement the following acts (including but not limited to) regarding this software and the information contained arbitrarily: use, lease, lend, replicate, modify, link, reprint, compile, release, publish, and establish mirror image website, and arbitrarily use this software to develop related derivative products, works, services, plug-ins, compatibility, interconnection, etc.;
Use this software to publish, transmit, spread and store contents violating local laws and regulations;
Use this software to publish, transmit, spread and store contents infringing others' intellectual property right, business secrete and other legal rights;
Use this software to publish, transmit and spread advertising information and junk information in batches;
Other acts of using this software and other services provided by ORPC in any illegal method, for any illegal purpose or by any means inconsistent with that permitted in this agreement;
4.2. Information release specification
You can use this software to release your original or entitled point of view, data, text, information, user name, picture, photo, personal information, audio, video document, link and other information contents. You must guarantee that you own intellectual property right or have obtained legal authorization concerning the uploaded information contents, and your use of this software and services do not infringe legal rights and interests of any third party.
You need to abide by requirements of local laws and regulations while using this software.
While using this software, you shall not use this software to engage in the following acts, including but not limited to: 1) produce, replicate, release, spread and store contents violating local laws and regulations; 2) release, transmit, spread and store contents infringing others' right of reputation, right of portrait, intellectual property right, business secrete and other legal rights; 3) make up and conceal facts to mislead and cheat others; 4) release, transmit and spread advertising information and junk information; 5) engage in other acts violating local laws and regulations.
Without written consent of ORPC, you shall not perform commercial acts such as publish advertisements and sell commodities in this software.
4.3. You understand and agree that:
ORPC will identify whether the users are suspected of violating the above use specification or not, and then suspend or terminate use license or take other restrictive measures that can be taken as agreed in this agreement;
As for the information that is suspected of being illegal or infringing legal rights of others or violating this agreement released by the users when using the licensed software, ORPC will delete directly;
If the users cause damages to third parties due to violating the above use specification, they should assume legal liabilities independently in their own name, and shall guarantee ORPC free from losses or increased expenses generated therefrom;
If the users violate relevant legal provisions or agreements, thus causing losses to ORPC, or receiving claims from third parties, or being punished by administrative organs, the users shall compensate for losses and (or) expenses of ORPC generated therefrom, including reasonable attorney fee and investigation and evidence collection fee.
V. Service risks and disclaimer
5.1. The users must equip themselves with intelligent mobile terminal equipment to surf the Internet and the equipment necessary for using telecom value-added business all by themselves, and assume communication expense, information fee and other relevant expenses for surfing Internet on personal mobile terminal equipment or charged by third parties independently.
5.2. For all losses suffered by the users due to third parties such as communication line failure, technical problem, network and mobile terminal equipment failure, unstable system and other various force majeure causes, ORPC and its cooperators assume no liabilities.
5.3. As most of Internet software, this software is subject to differential influence of factors including but not limited to causes of the users, network service quality, social environment and so on, other software downloaded or other websites accessed by the users contain "Trojan Horse" and other viruses, which threatens security of the users' terminal equipment information and data, and then influences normal use of this software and so on. The users shall enhance awareness of information security and user data protection, and shall pay attention to strengthening password protection, so as to avoid loss and harassment.
5.4. ORPC remind the users specially that, for the purpose of guaranteeing service upgrading and business development of ORPC, ORPC is entitled to modify or interrupt the software service at any time without notifying the users, and for service interruption or abnormality caused during the process of ORPC's adjusting the software service, ORPC does not assume any legal liabilities.
5.5. The personal injury or incidental and indirect economic damages including but not limited to profit loss, data loss, damages for business interruption or other commercial damages or losses due to or related to any of the following conditions of the users, shall be undertaken by the users independently.
Use of unlicensed software;
Due to reason of the users, third parties use the software or change data of the users without permission;
The users' expenses and losses due to use of this software for misconducts;
The users' misunderstanding of this software;
Other losses related with this software not due to ORPC.
5.6. For any personal or economic damages or losses caused or might be caused by the acts performed via this software by the users and other users using the software because you are misled or cheated, the fault party shall assume all liabilities, while ORPC does not assume any legal liability.
VI. Intellectual property right statement
6.1. ORPC legally owns all relevant intellectual property rights to this software system. All copyright, trademark, patent right, business secrete and other intellectual property rights of this software, and all information contents related with this software (including but not limited to text, picture, audio, video, chart, interface design, layout framework, relevant data or electronic document, etc.) are subject to protection of your local laws and regulations and corresponding international treaties.
6.2. Without written consent of ORPC, the users shall not independently or license any third party to implement, use and transfer the above intellectual property rights for any commercial or non-commercial purpose, and ORPC reserves the right to prosecute legal liabilities against the above acts.
VII. Change of agreement
7.1. ORPC is entitled to modify or change the charging services rendered, charging standard, charging method, charging fee and service terms. While rendering services, ORPC may now or in the future start to charge certain fees against the users for some services, and if the users refuse to pay such fees, they can't continue to use relevant services upon starting of the charging. ORPC and its cooperative corporations will try their best to inform the users of relevant modification or change by e-mail or other means.
VIII. Applicable laws and dispute resolution
8.1. Effectiveness and interpretation of clauses of this agreement are governed by local laws of the users. In case of no relevant legal provisions, international business practice and/or business practice shall prevail.
8.2. The users and ORPC agree with consensus that all disputes from using this software and corresponding services, shall be solved by both parties upon negotiation, and if negotiation fails, either party can submit the disputes to Shanghai Arbitration Commission for arbitration in accordance with its arbitration rules. The arbitral award is final, and is binding on both parties.
IX. Others
9.1. When using a specific service of this software, there might be separate agreement and related business rules, etc. regarding such service (hereinafter collectively referred to as "separate agreement"), please read and agree to relevant separate agreement before using such service.
9.2. This agreement shall take effect after the users accept this agreement or the users are deemed to accept this agreement.
9.3 If some clauses of this agreement are ineffective or unenforceable due to any reason, the remaining clauses shall still be effective and binding on both parties.


text:
The interview levels the playing field. No matter where you went to school, no matter what your GPA is, no matter how much experience you have, no matter who you know--if you aren't able to interview successfully, you won't get the job. Following are some insights designed to help you successfully interview and get the job you want--and then negotiate the very best job offer!
Preparing for the Interview
Interview "DOs" and "DON'Ts
Interview Sample Questions
Closing the Interview
Read more...
read more
© Copyright 2024 Edan Search Group. All rights reserved. Unauthorized duplication in part or whole strictly prohibited by international copyright law.

subset: commoncrawl


text:
SCSI mid_level - lower_level driver interface¶
This document outlines the interface between the Linux SCSI mid level and SCSI lower level drivers. Lower level drivers (LLDs) are variously called host bus adapter (HBA) drivers and host drivers (HD). A "host" in this context is a bridge between a computer IO bus (e.g. PCI or ISA) and a single SCSI initiator port on a SCSI transport. An "initiator" port (SCSI terminology, see SAM-3 at http://www.t10.org) sends SCSI commands to "target" SCSI ports (e.g. disks). There can be many LLDs in a running system, but only one per hardware type. Most LLDs can control one or more SCSI HBAs. Some HBAs contain multiple hosts.
In some cases the SCSI transport is an external bus that already has its own subsystem in Linux (e.g. USB and ieee1394). In such cases the SCSI subsystem LLD is a software bridge to the other driver subsystem. Examples are the usb-storage driver (found in the drivers/usb/storage directory) and the ieee1394/sbp2 driver (found in the drivers/ieee1394 directory).
For example, the aic7xxx LLD controls Adaptec SCSI parallel interface (SPI) controllers based on that company's 7xxx chip series. The aic7xxx LLD can be built into the kernel or loaded as a module. There can only be one aic7xxx LLD running in a Linux system but it may be controlling many HBAs. These HBAs might be either on PCI daughter-boards or built into the motherboard (or both). Some aic7xxx based HBAs are dual controllers and thus represent two hosts. Like most modern HBAs, each aic7xxx host has its own PCI device address. [The one-to-one correspondence between a SCSI host and a PCI device is common but not required (e.g. with ISA adapters).]
The SCSI mid level isolates an LLD from other layers such as the SCSI upper layer drivers and the block layer.
This version of the document roughly matches linux kernel version 2.6.8 .
There is a SCSI documentation directory within the kernel source tree, typically Documentation/scsi . Most documents are in plain (i.e. ASCII) text. This file is named SCSI mid_level - lower_level driver interface and can be found in that directory. A more recent copy of this document may be found at http://web.archive.org/web/20070107183357rn_1/sg.torque.net/scsi/. Many LLDs are documented there (e.g. Adaptec Aic7xxx Fast -> Ultra160 Family Manager Set v7.0). The SCSI mid-level is briefly described in SCSI subsystem documentation which contains a url to a document describing the SCSI subsystem in the lk 2.4 series. Two upper level drivers have documents in that directory: The SCSI Tape Driver (SCSI tape driver) and SCSI Generic (sg) driver (for the sg driver).
Some documentation (or urls) for LLDs may be found in the C source code or in the same directory as the C source code. For example to find a url about the USB mass storage driver see the /usr/src/linux/drivers/usb/storage directory.
Driver structure¶
Traditionally an LLD for the SCSI subsystem has been at least two files in the drivers/scsi directory. For example, a driver called "xyz" has a header file "xyz.h" and a source file "xyz.c". [Actually there is no good reason why this couldn't all be in one file; the header file is superfluous.] Some drivers that have been ported to several operating systems have more than two files. For example the aic7xxx driver has separate files for generic and OS-specific code (e.g. FreeBSD and Linux). Such drivers tend to have their own directory under the drivers/scsi directory.
When a new LLD is being added to Linux, the following files (found in the drivers/scsi directory) will need some attention: Makefile and Kconfig . It is probably best to study how existing LLDs are organized.
As the 2.5 series development kernels evolve into the 2.6 series production series, changes are being introduced into this interface. An example of this is driver initialization code where there are now 2 models available. The older one, similar to what was found in the lk 2.4 series, is based on hosts that are detected at HBA driver load time. This will be referred to the "passive" initialization model. The newer model allows HBAs to be hot plugged (and unplugged) during the lifetime of the LLD and will be referred to as the "hotplug" initialization model. The newer model is preferred as it can handle both traditional SCSI equipment that is permanently connected as well as modern "SCSI" devices (e.g. USB or IEEE 1394 connected digital cameras) that are hotplugged. Both initialization models are discussed in the following sections.
An LLD interfaces to the SCSI subsystem several ways:
directly invoking functions supplied by the mid level
passing a set of function pointers to a registration function supplied by the mid level. The mid level will then invoke these functions at some point in the future. The LLD will supply implementations of these functions.
direct access to instances of well known data structures maintained by the mid level
Those functions in group a) are listed in a section entitled "Mid level supplied functions" below.
Those functions in group b) are listed in a section entitled "Interface
functions" below. Their function pointers are placed in the members of
"struct scsi_host_template", an instance of which is passed to
1. Those interface functions that the LLD does not
wish to supply should have NULL placed in the corresponding member of
struct scsi_host_template. Defining an instance of struct
scsi_host_template at file scope will cause NULL to be placed in function
pointer members not explicitly initialized.
Those usages in group c) should be handled with care, especially in a "hotplug" environment. LLDs should be aware of the lifetime of instances that are shared with the mid level and other layers.
All functions defined within an LLD and all data defined at file scope
should be static. For example the slave_alloc() function in an LLD
called "xxx" could be defined as
static int xxx_slave_alloc(struct scsi_device * sdev) { /* code */ }
- 1
function is a replacement for the rather vaguely named scsi_register() function in most situations.
Hotplug initialization model¶
In this model an LLD controls when SCSI hosts are introduced and removed from the SCSI subsystem. Hosts can be introduced as early as driver initialization and removed as late as driver shutdown. Typically a driver will respond to a sysfs probe() callback that indicates an HBA has been detected. After confirming that the new device is one that the LLD wants to control, the LLD will initialize the HBA and then register a new host with the SCSI mid level.
During LLD initialization the driver should register itself with the appropriate IO bus on which it expects to find HBA(s) (e.g. the PCI bus). This can probably be done via sysfs. Any driver parameters (especially those that are writable after the driver is loaded) could also be registered with sysfs at this point. The SCSI mid level first becomes aware of an LLD when that LLD registers its first HBA.
At some later time, the LLD becomes aware of an HBA and what follows is a typical sequence of calls between the LLD and the mid level. This example shows the mid level scanning the newly introduced HBA for 3 scsi devices of which only the first 2 respond:
HBA PROBE: assume 2 SCSI devices found in scan
LLD mid level LLD
scsi_host_alloc() -->
scsi_add_host() ---->
scsi_scan_host() -------+
slave_configure() --> scsi_change_queue_depth()
slave_alloc() ***
slave_destroy() ***
*** For scsi devices that the mid level tries to scan but do not
respond, a slave_alloc(), slave_destroy() pair is called.
If the LLD wants to adjust the default queue settings, it can invoke
in its slave_configure() routine.
When an HBA is being removed it could be as part of an orderly shutdown associated with the LLD module being unloaded (e.g. with the "rmmod" command) or in response to a "hot unplug" indicated by sysfs()'s remove() callback being invoked. In either case, the sequence is the same:
HBA REMOVE: assume 2 SCSI devices attached
LLD mid level LLD
scsi_remove_host() ---------+
It may be useful for a LLD to keep track of struct Scsi_Host instances
(a pointer is returned by scsi_host_alloc()
). Such instances are "owned"
by the mid-level. struct Scsi_Host instances are freed from
when the reference count hits zero.
Hot unplugging an HBA that controls a disk which is processing SCSI commands on a mounted file system is an interesting situation. Reference counting logic is being introduced into the mid level to cope with many of the issues involved. See the section on reference counting below.
The hotplug concept may be extended to SCSI devices. Currently, when an HBA is added, the scsi_scan_host() function causes a scan for SCSI devices attached to the HBA's SCSI transport. On newer SCSI transports the HBA may become aware of a new SCSI device _after_ the scan has completed. An LLD can use this sequence to make the mid level aware of a SCSI device:
SCSI DEVICE hotplug
LLD mid level LLD
scsi_add_device() ------+
slave_configure() [--> scsi_change_queue_depth()]
In a similar fashion, an LLD may become aware that a SCSI device has been removed (unplugged) or the connection to it has been interrupted. Some existing SCSI transports (e.g. SPI) may not become aware that a SCSI device has been removed until a subsequent SCSI command fails which will probably cause that device to be set offline by the mid level. An LLD that detects the removal of a SCSI device can instigate its removal from upper layers with this sequence:
SCSI DEVICE hot unplug
LLD mid level LLD
scsi_remove_device() -------+
It may be useful for an LLD to keep track of struct scsi_device instances (a pointer is passed as the parameter to slave_alloc() and slave_configure() callbacks). Such instances are "owned" by the mid-level. struct scsi_device instances are freed after slave_destroy().
Reference Counting¶
The Scsi_Host structure has had reference counting infrastructure added. This effectively spreads the ownership of struct Scsi_Host instances across the various SCSI layers which use them. Previously such instances were exclusively owned by the mid level. LLDs would not usually need to directly manipulate these reference counts but there may be some cases where they do.
There are 3 reference counting functions of interest associated with struct Scsi_Host:
- scsi_host_alloc():
returns a pointer to new instance of struct Scsi_Host which has its reference count ^^ set to 1
- scsi_host_get():
adds 1 to the reference count of the given instance
- scsi_host_put():
decrements 1 from the reference count of the given instance. If the reference count reaches 0 then the given instance is freed
The scsi_device structure has had reference counting infrastructure added.
This effectively spreads the ownership of struct scsi_device instances
across the various SCSI layers which use them. Previously such instances
were exclusively owned by the mid level. See the access functions declared
towards the end of include/scsi/scsi_device.h . If an LLD wants to keep
a copy of a pointer to a scsi_device instance it should use scsi_device_get()
to bump its reference count. When it is finished with the pointer it can
use scsi_device_put()
to decrement its reference count (and potentially
delete it).
struct Scsi_Host actually has 2 reference counts which are manipulated in parallel by these functions.
First, Linus Torvalds's thoughts on C coding style can be found in the Linux kernel coding style file.
Also, most C99 enhancements are encouraged to the extent they are supported
by the relevant gcc compilers. So C99 style structure and array
initializers are encouraged where appropriate. Don't go too far,
VLAs are not properly supported yet. An exception to this is the use of
style comments; /*...*/
comments are still preferred in Linux.
Well written, tested and documented code, need not be re-formatted to comply with the above conventions. For example, the aic7xxx driver comes to Linux from FreeBSD and Adaptec's own labs. No doubt FreeBSD and Adaptec have their own coding conventions.
Mid level supplied functions¶
These functions are supplied by the SCSI mid level for use by LLDs.
The names (i.e. entry points) of these functions are exported
so an LLD that is a module can access them. The kernel will
arrange for the SCSI mid level to be loaded and initialized before any LLD
is initialized. The functions below are listed alphabetically and their
names all start with scsi_
scsi_add_device - creates new scsi device (lu) instance
scsi_add_host - perform sysfs registration and set up transport class
scsi_change_queue_depth - change the queue depth on a SCSI device
scsi_bios_ptable - return copy of block device's partition table
scsi_block_requests - prevent further commands being queued to given host
scsi_host_alloc - return a new scsi_host instance whose refcount==1
scsi_host_get - increments Scsi_Host instance's refcount
scsi_host_put - decrements Scsi_Host instance's refcount (free if 0)
scsi_register - create and register a scsi host adapter instance.
scsi_remove_device - detach and remove a SCSI device
scsi_remove_host - detach and remove all SCSI devices owned by host
scsi_report_bus_reset - report scsi _bus_ reset observed
scsi_scan_host - scan SCSI bus
scsi_track_queue_full - track successive QUEUE_FULL events
scsi_unblock_requests - allow further commands to be queued to given host
scsi_unregister - [calls
* scsi_add_device - creates new scsi device (lu) instance
* @shost: pointer to scsi host instance
* @channel: channel number (rarely other than 0)
* @id: target id number
* @lun: logical unit number
* Returns pointer to new struct scsi_device instance or
* ERR_PTR(-ENODEV) (or some other bent pointer) if something is
* wrong (e.g. no lu responds at given address)
* Might block: yes
* Notes: This call is usually performed internally during a scsi
* bus scan when an HBA is added (i.e. scsi_scan_host()). So it
* should only be called if the HBA becomes aware of a new scsi
* device (lu) after scsi_scan_host() has completed. If successful
* this call can lead to slave_alloc() and slave_configure() callbacks
* into the LLD.
* Defined in: drivers/scsi/scsi_scan.c
struct scsi_device * scsi_add_device(struct Scsi_Host *shost,
unsigned int channel,
unsigned int id, unsigned int lun)
* scsi_add_host - perform sysfs registration and set up transport class
* @shost: pointer to scsi host instance
* @dev: pointer to struct device of type scsi class
* Returns 0 on success, negative errno of failure (e.g. -ENOMEM)
* Might block: no
* Notes: Only required in "hotplug initialization model" after a
* successful call to scsi_host_alloc(). This function does not
* scan the bus; this can be done by calling scsi_scan_host() or
* in some other transport-specific way. The LLD must set up
* the transport template before calling this function and may only
* access the transport class data after this function has been called.
* Defined in: drivers/scsi/hosts.c
int scsi_add_host(struct Scsi_Host *shost, struct device * dev)
* scsi_change_queue_depth - allow LLD to change queue depth on a SCSI device
* @sdev: pointer to SCSI device to change queue depth on
* @tags Number of tags allowed if tagged queuing enabled,
* or number of commands the LLD can queue up
* in non-tagged mode (as per cmd_per_lun).
* Returns nothing
* Might block: no
* Notes: Can be invoked any time on a SCSI device controlled by this
* LLD. [Specifically during and after slave_configure() and prior to
* slave_destroy().] Can safely be invoked from interrupt code.
* Defined in: drivers/scsi/scsi.c [see source code for more notes]
int scsi_change_queue_depth(struct scsi_device *sdev, int tags)
* scsi_bios_ptable - return copy of block device's partition table
* @dev: pointer to block device
* Returns pointer to partition table, or NULL for failure
* Might block: yes
* Notes: Caller owns memory returned (free with kfree() )
* Defined in: drivers/scsi/scsicam.c
unsigned char *scsi_bios_ptable(struct block_device *dev)
* scsi_block_requests - prevent further commands being queued to given host
* @shost: pointer to host to block commands on
* Returns nothing
* Might block: no
* Notes: There is no timer nor any other means by which the requests
* get unblocked other than the LLD calling scsi_unblock_requests().
* Defined in: drivers/scsi/scsi_lib.c
void scsi_block_requests(struct Scsi_Host * shost)
* scsi_host_alloc - create a scsi host adapter instance and perform basic
* initialization.
* @sht: pointer to scsi host template
* @privsize: extra bytes to allocate in hostdata array (which is the
* last member of the returned Scsi_Host instance)
* Returns pointer to new Scsi_Host instance or NULL on failure
* Might block: yes
* Notes: When this call returns to the LLD, the SCSI bus scan on
* this host has _not_ yet been done.
* The hostdata array (by default zero length) is a per host scratch
* area for the LLD's exclusive use.
* Both associated refcounting objects have their refcount set to 1.
* Full registration (in sysfs) and a bus scan are performed later when
* scsi_add_host() and scsi_scan_host() are called.
* Defined in: drivers/scsi/hosts.c .
struct Scsi_Host * scsi_host_alloc(const struct scsi_host_template * sht,
int privsize)
* scsi_host_get - increment Scsi_Host instance refcount
* @shost: pointer to struct Scsi_Host instance
* Returns nothing
* Might block: currently may block but may be changed to not block
* Notes: Actually increments the counts in two sub-objects
* Defined in: drivers/scsi/hosts.c
void scsi_host_get(struct Scsi_Host *shost)
* scsi_host_put - decrement Scsi_Host instance refcount, free if 0
* @shost: pointer to struct Scsi_Host instance
* Returns nothing
* Might block: currently may block but may be changed to not block
* Notes: Actually decrements the counts in two sub-objects. If the
* latter refcount reaches 0, the Scsi_Host instance is freed.
* The LLD need not worry exactly when the Scsi_Host instance is
* freed, it just shouldn't access the instance after it has balanced
* out its refcount usage.
* Defined in: drivers/scsi/hosts.c
void scsi_host_put(struct Scsi_Host *shost)
* scsi_register - create and register a scsi host adapter instance.
* @sht: pointer to scsi host template
* @privsize: extra bytes to allocate in hostdata array (which is the
* last member of the returned Scsi_Host instance)
* Returns pointer to new Scsi_Host instance or NULL on failure
* Might block: yes
* Notes: When this call returns to the LLD, the SCSI bus scan on
* this host has _not_ yet been done.
* The hostdata array (by default zero length) is a per host scratch
* area for the LLD.
* Defined in: drivers/scsi/hosts.c .
struct Scsi_Host * scsi_register(struct scsi_host_template * sht,
int privsize)
* scsi_remove_device - detach and remove a SCSI device
* @sdev: a pointer to a scsi device instance
* Returns value: 0 on success, -EINVAL if device not attached
* Might block: yes
* Notes: If an LLD becomes aware that a scsi device (lu) has
* been removed but its host is still present then it can request
* the removal of that scsi device. If successful this call will
* lead to the slave_destroy() callback being invoked. sdev is an
* invalid pointer after this call.
* Defined in: drivers/scsi/scsi_sysfs.c .
int scsi_remove_device(struct scsi_device *sdev)
* scsi_remove_host - detach and remove all SCSI devices owned by host
* @shost: a pointer to a scsi host instance
* Returns value: 0 on success, 1 on failure (e.g. LLD busy ??)
* Might block: yes
* Notes: Should only be invoked if the "hotplug initialization
* model" is being used. It should be called _prior_ to
* scsi_unregister().
* Defined in: drivers/scsi/hosts.c .
int scsi_remove_host(struct Scsi_Host *shost)
* scsi_report_bus_reset - report scsi _bus_ reset observed
* @shost: a pointer to a scsi host involved
* @channel: channel (within) host on which scsi bus reset occurred
* Returns nothing
* Might block: no
* Notes: This only needs to be called if the reset is one which
* originates from an unknown location. Resets originated by the
* mid level itself don't need to call this, but there should be
* no harm. The main purpose of this is to make sure that a
* CHECK_CONDITION is properly treated.
* Defined in: drivers/scsi/scsi_error.c .
void scsi_report_bus_reset(struct Scsi_Host * shost, int channel)
* scsi_scan_host - scan SCSI bus
* @shost: a pointer to a scsi host instance
* Might block: yes
* Notes: Should be called after scsi_add_host()
* Defined in: drivers/scsi/scsi_scan.c
void scsi_scan_host(struct Scsi_Host *shost)
* scsi_track_queue_full - track successive QUEUE_FULL events on given
* device to determine if and when there is a need
* to adjust the queue depth on the device.
* @sdev: pointer to SCSI device instance
* @depth: Current number of outstanding SCSI commands on this device,
* not counting the one returned as QUEUE_FULL.
* Returns 0 - no change needed
* >0 - adjust queue depth to this new depth
* -1 - drop back to untagged operation using host->cmd_per_lun
* as the untagged command depth
* Might block: no
* Notes: LLDs may call this at any time and we will do "The Right
* Thing"; interrupt context safe.
* Defined in: drivers/scsi/scsi.c .
int scsi_track_queue_full(struct scsi_device *sdev, int depth)
* scsi_unblock_requests - allow further commands to be queued to given host
* @shost: pointer to host to unblock commands on
* Returns nothing
* Might block: no
* Defined in: drivers/scsi/scsi_lib.c .
void scsi_unblock_requests(struct Scsi_Host * shost)
* scsi_unregister - unregister and free memory used by host instance
* @shp: pointer to scsi host instance to unregister.
* Returns nothing
* Might block: no
* Notes: Should not be invoked if the "hotplug initialization
* model" is being used. Called internally by exit_this_scsi_driver()
* in the "passive initialization model". Hence a LLD has no need to
* call this function directly.
* Defined in: drivers/scsi/hosts.c .
void scsi_unregister(struct Scsi_Host * shp)
Interface Functions¶
Interface functions are supplied (defined) by LLDs and their function
pointers are placed in an instance of struct scsi_host_template which
is passed to scsi_host_alloc()
[or scsi_register() / init_this_scsi_driver()].
Some are mandatory. Interface functions should be declared static. The
accepted convention is that driver "xyz" will declare its slave_configure()
function as:
static int xyz_slave_configure(struct scsi_device * sdev);
and so forth for all interface functions listed below.
A pointer to this function should be placed in the 'slave_configure' member
of a "struct scsi_host_template" instance. A pointer to such an instance
should be passed to the mid level's scsi_host_alloc()
[or scsi_register() /
The interface functions are also described in the include/scsi/scsi_host.h file immediately above their definition point in "struct scsi_host_template". In some cases more detail is given in scsi_host.h than below.
The interface functions are listed below in alphabetical order.
bios_param - fetch head, sector, cylinder info for a disk
eh_timed_out - notify the host that a command timer expired
eh_abort_handler - abort given command
eh_bus_reset_handler - issue SCSI bus reset
eh_device_reset_handler - issue SCSI device reset
eh_host_reset_handler - reset host (host bus adapter)
info - supply information about given host
ioctl - driver can respond to ioctls
proc_info - supports /proc/scsi/{driver_name}/{host_no}
queuecommand - queue scsi command, invoke 'done' on completion
slave_alloc - prior to any commands being sent to a new device
slave_configure - driver fine tuning for given device after attach
slave_destroy - given device is about to be shut down
* bios_param - fetch head, sector, cylinder info for a disk
* @sdev: pointer to scsi device context (defined in
* include/scsi/scsi_device.h)
* @bdev: pointer to block device context (defined in fs.h)
* @capacity: device size (in 512 byte sectors)
* @params: three element array to place output:
* params[0] number of heads (max 255)
* params[1] number of sectors (max 63)
* params[2] number of cylinders
* Return value is ignored
* Locks: none
* Calling context: process (sd)
* Notes: an arbitrary geometry (based on READ CAPACITY) is used
* if this function is not provided. The params array is
* pre-initialized with made up values just in case this function
* doesn't output anything.
* Optionally defined in: LLD
int bios_param(struct scsi_device * sdev, struct block_device *bdev,
sector_t capacity, int params[3])
* eh_timed_out - The timer for the command has just fired
* @scp: identifies command timing out
* Returns:
* EH_HANDLED: I fixed the error, please complete the command
* EH_RESET_TIMER: I need more time, reset the timer and
* begin counting again
* EH_NOT_HANDLED Begin normal error recovery
* Locks: None held
* Calling context: interrupt
* Notes: This is to give the LLD an opportunity to do local recovery.
* This recovery is limited to determining if the outstanding command
* will ever complete. You may not abort and restart the command from
* this callback.
* Optionally defined in: LLD
int eh_timed_out(struct scsi_cmnd * scp)
* eh_abort_handler - abort command associated with scp
* @scp: identifies command to be aborted
* Returns SUCCESS if command aborted else FAILED
* Locks: None held
* Calling context: kernel thread
* Notes: If 'no_async_abort' is defined this callback
* will be invoked from scsi_eh thread. No other commands
* will then be queued on current host during eh.
* Otherwise it will be called whenever scsi_timeout()
* is called due to a command timeout.
* Optionally defined in: LLD
int eh_abort_handler(struct scsi_cmnd * scp)
* eh_bus_reset_handler - issue SCSI bus reset
* @scp: SCSI bus that contains this device should be reset
* Returns SUCCESS if command aborted else FAILED
* Locks: None held
* Calling context: kernel thread
* Notes: Invoked from scsi_eh thread. No other commands will be
* queued on current host during eh.
* Optionally defined in: LLD
int eh_bus_reset_handler(struct scsi_cmnd * scp)
* eh_device_reset_handler - issue SCSI device reset
* @scp: identifies SCSI device to be reset
* Returns SUCCESS if command aborted else FAILED
* Locks: None held
* Calling context: kernel thread
* Notes: Invoked from scsi_eh thread. No other commands will be
* queued on current host during eh.
* Optionally defined in: LLD
int eh_device_reset_handler(struct scsi_cmnd * scp)
* eh_host_reset_handler - reset host (host bus adapter)
* @scp: SCSI host that contains this device should be reset
* Returns SUCCESS if command aborted else FAILED
* Locks: None held
* Calling context: kernel thread
* Notes: Invoked from scsi_eh thread. No other commands will be
* queued on current host during eh.
* With the default eh_strategy in place, if none of the _abort_,
* _device_reset_, _bus_reset_ or this eh handler function are
* defined (or they all return FAILED) then the device in question
* will be set offline whenever eh is invoked.
* Optionally defined in: LLD
int eh_host_reset_handler(struct scsi_cmnd * scp)
* info - supply information about given host: driver name plus data
* to distinguish given host
* @shp: host to supply information about
* Return ASCII null terminated string. [This driver is assumed to
* manage the memory pointed to and maintain it, typically for the
* lifetime of this host.]
* Locks: none
* Calling context: process
* Notes: Often supplies PCI or ISA information such as IO addresses
* and interrupt numbers. If not supplied struct Scsi_Host::name used
* instead. It is assumed the returned information fits on one line
* (i.e. does not included embedded newlines).
* The SCSI_IOCTL_PROBE_HOST ioctl yields the string returned by this
* function (or struct Scsi_Host::name if this function is not
* available).
* In a similar manner, init_this_scsi_driver() outputs to the console
* each host's "info" (or name) for the driver it is registering.
* Also if proc_info() is not supplied, the output of this function
* is used instead.
* Optionally defined in: LLD
const char * info(struct Scsi_Host * shp)
* ioctl - driver can respond to ioctls
* @sdp: device that ioctl was issued for
* @cmd: ioctl number
* @arg: pointer to read or write data from. Since it points to
* user space, should use appropriate kernel functions
* (e.g. copy_from_user() ). In the Unix style this argument
* can also be viewed as an unsigned long.
* Returns negative "errno" value when there is a problem. 0 or a
* positive value indicates success and is returned to the user space.
* Locks: none
* Calling context: process
* Notes: The SCSI subsystem uses a "trickle down" ioctl model.
* The user issues an ioctl() against an upper level driver
* (e.g. /dev/sdc) and if the upper level driver doesn't recognize
* the 'cmd' then it is passed to the SCSI mid level. If the SCSI
* mid level does not recognize it, then the LLD that controls
* the device receives the ioctl. According to recent Unix standards
* unsupported ioctl() 'cmd' numbers should return -ENOTTY.
* Optionally defined in: LLD
int ioctl(struct scsi_device *sdp, int cmd, void *arg)
* proc_info - supports /proc/scsi/{driver_name}/{host_no}
* @buffer: anchor point to output to (0==writeto1_read0) or fetch from
* (1==writeto1_read0).
* @start: where "interesting" data is written to. Ignored when
* 1==writeto1_read0.
* @offset: offset within buffer 0==writeto1_read0 is actually
* interested in. Ignored when 1==writeto1_read0 .
* @length: maximum (or actual) extent of buffer
* @host_no: host number of interest (struct Scsi_Host::host_no)
* @writeto1_read0: 1 -> data coming from user space towards driver
* (e.g. "echo some_string > /proc/scsi/xyz/2")
* 0 -> user what data from this driver
* (e.g. "cat /proc/scsi/xyz/2")
* Returns length when 1==writeto1_read0. Otherwise number of chars
* output to buffer past offset.
* Locks: none held
* Calling context: process
* Notes: Driven from scsi_proc.c which interfaces to proc_fs. proc_fs
* support can now be configured out of the scsi subsystem.
* Optionally defined in: LLD
int proc_info(char * buffer, char ** start, off_t offset,
int length, int host_no, int writeto1_read0)
* queuecommand - queue scsi command, invoke scp->scsi_done on completion
* @shost: pointer to the scsi host object
* @scp: pointer to scsi command object
* Returns 0 on success.
* If there's a failure, return either:
* SCSI_MLQUEUE_DEVICE_BUSY if the device queue is full, or
* SCSI_MLQUEUE_HOST_BUSY if the entire host queue is full
* On both of these returns, the mid-layer will requeue the I/O
* - if the return is SCSI_MLQUEUE_DEVICE_BUSY, only that particular
* device will be paused, and it will be unpaused when a command to
* the device returns (or after a brief delay if there are no more
* outstanding commands to it). Commands to other devices continue
* to be processed normally.
* - if the return is SCSI_MLQUEUE_HOST_BUSY, all I/O to the host
* is paused and will be unpaused when any command returns from
* the host (or after a brief delay if there are no outstanding
* commands to the host).
* For compatibility with earlier versions of queuecommand, any
* other return value is treated the same as
* Other types of errors that are detected immediately may be
* flagged by setting scp->result to an appropriate value,
* invoking the scp->scsi_done callback, and then returning 0
* from this function. If the command is not performed
* immediately (and the LLD is starting (or will start) the given
* command) then this function should place 0 in scp->result and
* return 0.
* Command ownership. If the driver returns zero, it owns the
* command and must take responsibility for ensuring the
* scp->scsi_done callback is executed. Note: the driver may
* call scp->scsi_done before returning zero, but after it has
* called scp->scsi_done, it may not return any value other than
* zero. If the driver makes a non-zero return, it must not
* execute the command's scsi_done callback at any time.
* Locks: up to and including 2.6.36, struct Scsi_Host::host_lock
* held on entry (with "irqsave") and is expected to be
* held on return. From 2.6.37 onwards, queuecommand is
* called without any locks held.
* Calling context: in interrupt (soft irq) or process context
* Notes: This function should be relatively fast. Normally it
* will not wait for IO to complete. Hence the scp->scsi_done
* callback is invoked (often directly from an interrupt service
* routine) some time after this function has returned. In some
* cases (e.g. pseudo adapter drivers that manufacture the
* response to a SCSI INQUIRY) the scp->scsi_done callback may be
* invoked before this function returns. If the scp->scsi_done
* callback is not invoked within a certain period the SCSI mid
* level will commence error processing. If a status of CHECK
* CONDITION is placed in "result" when the scp->scsi_done
* callback is invoked, then the LLD driver should perform
* autosense and fill in the struct scsi_cmnd::sense_buffer
* array. The scsi_cmnd::sense_buffer array is zeroed prior to
* the mid level queuing a command to an LLD.
* Defined in: LLD
int queuecommand(struct Scsi_Host *shost, struct scsi_cmnd * scp)
* slave_alloc - prior to any commands being sent to a new device
* (i.e. just prior to scan) this call is made
* @sdp: pointer to new device (about to be scanned)
* Returns 0 if ok. Any other return is assumed to be an error and
* the device is ignored.
* Locks: none
* Calling context: process
* Notes: Allows the driver to allocate any resources for a device
* prior to its initial scan. The corresponding scsi device may not
* exist but the mid level is just about to scan for it (i.e. send
* and INQUIRY command plus ...). If a device is found then
* slave_configure() will be called while if a device is not found
* slave_destroy() is called.
* For more details see the include/scsi/scsi_host.h file.
* Optionally defined in: LLD
int slave_alloc(struct scsi_device *sdp)
* slave_configure - driver fine tuning for given device just after it
* has been first scanned (i.e. it responded to an
* @sdp: device that has just been attached
* Returns 0 if ok. Any other return is assumed to be an error and
* the device is taken offline. [offline devices will _not_ have
* slave_destroy() called on them so clean up resources.]
* Locks: none
* Calling context: process
* Notes: Allows the driver to inspect the response to the initial
* INQUIRY done by the scanning code and take appropriate action.
* For more details see the include/scsi/scsi_host.h file.
* Optionally defined in: LLD
int slave_configure(struct scsi_device *sdp)
* slave_destroy - given device is about to be shut down. All
* activity has ceased on this device.
* @sdp: device that is about to be shut down
* Returns nothing
* Locks: none
* Calling context: process
* Notes: Mid level structures for given device are still in place
* but are about to be torn down. Any per device resources allocated
* by this driver for given device should be freed now. No further
* commands will be sent for this sdp instance. [However the device
* could be re-attached in the future in which case a new instance
* of struct scsi_device would be supplied by future slave_alloc()
* and slave_configure() calls.]
* Optionally defined in: LLD
void slave_destroy(struct scsi_device *sdp)
Data Structures¶
struct scsi_host_template¶
There is one "struct scsi_host_template" instance per LLD 2. It is typically initialized as a file scope static in a driver's header file. That way members that are not explicitly initialized will be set to 0 or NULL. Member of interest:
- name
name of driver (may contain spaces, please limit to less than 80 characters)
- proc_name
name used in "/proc/scsi/<proc_name>/<host_no>" and by sysfs in one of its "drivers" directories. Hence "proc_name" should only contain characters acceptable to a Unix file name.
primary callback that the mid level uses to inject SCSI commands into an LLD.
The structure is defined and commented in include/scsi/scsi_host.h
- 2
In extreme situations a single driver may have several instances if it controls several different classes of hardware (e.g. an LLD that handles both ISA and PCI cards and has a separate instance of struct scsi_host_template for each class).
struct Scsi_Host¶
There is one struct Scsi_Host instance per host (HBA) that an LLD
controls. The struct Scsi_Host structure has many members in common
with "struct scsi_host_template". When a new struct Scsi_Host instance
is created (in scsi_host_alloc()
in hosts.c) those common members are
initialized from the driver's struct scsi_host_template instance. Members
of interest:
- host_no
system wide unique number that is used for identifying this host. Issued in ascending order from 0.
- can_queue
must be greater than 0; do not send more than can_queue commands to the adapter.
- this_id
scsi id of host (scsi initiator) or -1 if not known
- sg_tablesize
maximum scatter gather elements allowed by host. Set this to SG_ALL or less to avoid chained SG lists. Must be at least 1.
- max_sectors
maximum number of sectors (usually 512 bytes) allowed in a single SCSI command. The default value of 0 leads to a setting of SCSI_DEFAULT_MAX_SECTORS (defined in scsi_host.h) which is currently set to 1024. So for a disk the maximum transfer size is 512 KB when max_sectors is not defined. Note that this size may not be sufficient for disk firmware uploads.
- cmd_per_lun
maximum number of commands that can be queued on devices controlled by the host. Overridden by LLD calls to
.- no_async_abort
1=>Asynchronous aborts are not supported
0=>Timed-out commands will be aborted asynchronously
- hostt
pointer to driver's struct scsi_host_template from which this struct Scsi_Host instance was spawned
- hostt->proc_name
name of LLD. This is the driver name that sysfs uses
- transportt
pointer to driver's struct scsi_transport_template instance (if any). FC and SPI transports currently supported.
- sh_list
a double linked list of pointers to all struct Scsi_Host instances (currently ordered by ascending host_no)
- my_devices
a double linked list of pointers to struct scsi_device instances that belong to this host.
- hostdata[0]
area reserved for LLD at end of struct Scsi_Host. Size is set by the second argument (named 'xtr_bytes') to
or scsi_register().- vendor_id
a unique value that identifies the vendor supplying the LLD for the Scsi_Host. Used most often in validating vendor-specific message requests. Value consists of an identifier type and a vendor-specific value. See scsi_netlink.h for a description of valid formats.
The scsi_host structure is defined in include/scsi/scsi_host.h
struct scsi_device¶
Generally, there is one instance of this structure for each SCSI logical unit on a host. Scsi devices connected to a host are uniquely identified by a channel number, target id and logical unit number (lun). The structure is defined in include/scsi/scsi_device.h
struct scsi_cmnd¶
Instances of this structure convey SCSI commands to the LLD and responses
back to the mid level. The SCSI mid level will ensure that no more SCSI
commands become queued against the LLD than are indicated by
(or struct Scsi_Host::cmd_per_lun). There will
be at least one instance of struct scsi_cmnd available for each SCSI device.
Members of interest:
- cmnd
array containing SCSI command
- cmnd_len
length (in bytes) of SCSI command
- sc_data_direction
direction of data transfer in data phase. See "enum dma_data_direction" in include/linux/dma-mapping.h
- request_bufflen
number of data bytes to transfer (0 if no data phase)
- use_sg
- ==0 -> no scatter gather list, hence transfer data
to/from request_buffer
- >0 -> scatter gather list (actually an array) in
request_buffer with use_sg elements
- request_buffer
either contains data buffer or scatter gather list depending on the setting of use_sg. Scatter gather elements are defined by 'struct scatterlist' found in include/linux/scatterlist.h .
- done
function pointer that should be invoked by LLD when the SCSI command is completed (successfully or otherwise). Should only be called by an LLD if the LLD has accepted the command (i.e. queuecommand() returned or will return 0). The LLD may invoke 'done' prior to queuecommand() finishing.
- result
should be set by LLD prior to calling 'done'. A value of 0 implies a successfully completed command (and all data (if any) has been transferred to or from the SCSI target device). 'result' is a 32 bit unsigned integer that can be viewed as 2 related bytes. The SCSI status value is in the LSB. See include/scsi/scsi.h status_byte() and host_byte() macros and related constants.
- sense_buffer
an array (maximum size: SCSI_SENSE_BUFFERSIZE bytes) that should be written when the SCSI status (LSB of 'result') is set to CHECK_CONDITION (2). When CHECK_CONDITION is set, if the top nibble of sense_buffer[0] has the value 7 then the mid level will assume the sense_buffer array contains a valid SCSI sense buffer; otherwise the mid level will issue a REQUEST_SENSE SCSI command to retrieve the sense buffer. The latter strategy is error prone in the presence of command queuing so the LLD should always "auto-sense".
- device
pointer to scsi_device object that this command is associated with.
- resid
an LLD should set this signed integer to the requested transfer length (i.e. 'request_bufflen') less the number of bytes that are actually transferred. 'resid' is preset to 0 so an LLD can ignore it if it cannot detect underruns (overruns should be rare). If possible an LLD should set 'resid' prior to invoking 'done'. The most interesting case is data transfers from a SCSI target device (e.g. READs) that underrun.
- underflow
LLD should place (DID_ERROR << 16) in 'result' if actual number of bytes transferred is less than this figure. Not many LLDs implement this check and some that do just output an error message to the log rather than report a DID_ERROR. Better for an LLD to implement 'resid'.
It is recommended that a LLD set 'resid' on data transfers from a SCSI target device (e.g. READs). It is especially important that 'resid' is set when such data transfers have sense keys of MEDIUM ERROR and HARDWARE ERROR (and possibly RECOVERED ERROR). In these cases if a LLD is in doubt how much data has been received then the safest approach is to indicate no bytes have been received. For example: to indicate that no valid data has been received a LLD might use these helpers:
scsi_set_resid(SCpnt, scsi_bufflen(SCpnt));
where 'SCpnt' is a pointer to a scsi_cmnd object. To indicate only three 512 bytes blocks has been received 'resid' could be set like this:
scsi_set_resid(SCpnt, scsi_bufflen(SCpnt) - (3 * 512));
The scsi_cmnd structure is defined in include/scsi/scsi_cmnd.h
Each struct Scsi_Host instance has a spin_lock called struct
Scsi_Host::default_lock which is initialized in scsi_host_alloc()
[found in
hosts.c]. Within the same function the struct Scsi_Host::host_lock pointer
is initialized to point at default_lock. Thereafter lock and unlock
operations performed by the mid level use the struct Scsi_Host::host_lock
pointer. Previously drivers could override the host_lock pointer but
this is not allowed anymore.
Autosense (or auto-sense) is defined in the SAM-2 document as "the automatic return of sense data to the application client coincident with the completion of a SCSI command" when a status of CHECK CONDITION occurs. LLDs should perform autosense. This should be done when the LLD detects a CHECK CONDITION status by either:
instructing the SCSI protocol (e.g. SCSI Parallel Interface (SPI)) to perform an extra data in phase on such responses
or, the LLD issuing a REQUEST SENSE command itself
Either way, when a status of CHECK CONDITION is detected, the mid level decides whether the LLD has performed autosense by checking struct scsi_cmnd::sense_buffer[0] . If this byte has an upper nibble of 7 (or 0xf) then autosense is assumed to have taken place. If it has another value (and this byte is initialized to 0 before each command) then the mid level will issue a REQUEST SENSE command.
In the presence of queued commands the "nexus" that maintains sense buffer data from the command that failed until a following REQUEST SENSE may get out of synchronization. This is why it is best for the LLD to perform autosense.
Changes since lk 2.4 series¶
io_request_lock has been replaced by several finer grained locks. The lock relevant to LLDs is struct Scsi_Host::host_lock and there is one per SCSI host.
The older error handling mechanism has been removed. This means the LLD interface functions abort() and reset() have been removed. The struct scsi_host_template::use_new_eh_code flag has been removed.
In the 2.4 series the SCSI subsystem configuration descriptions were aggregated with the configuration descriptions from all other Linux subsystems in the Documentation/Configure.help file. In the 2.6 series, the SCSI subsystem now has its own (much smaller) drivers/scsi/Kconfig file that contains both configuration and help information.
struct SHT has been renamed to struct scsi_host_template.
Addition of the "hotplug initialization model" and many extra functions to support it.
The following people have contributed to this document:
Mike Anderson <andmike at us dot ibm dot com>
James Bottomley <James dot Bottomley at hansenpartnership dot com>
Patrick Mansfield <patmans at us dot ibm dot com>
Christoph Hellwig <hch at infradead dot org>
Doug Ledford <dledford at redhat dot com>
Andries Brouwer <Andries dot Brouwer at cwi dot nl>
Randy Dunlap <rdunlap at xenotime dot net>
Alan Stern <stern at rowland dot harvard dot edu>
Douglas Gilbert dgilbert at interlog dot com
21st September 2004


text: We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! ** Changed in: dhcp3 (Ubuntu) Status: Incomplete => Invalid -- Running dhclient after install generates (non-critical) error https://bugs.launchpad.net/bugs/88447 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dhcp3 in ubuntu.


text:
Enhance the interior of your Mitsubishi Pajero 4th Generation with our premium curtains, designed to elevate your driving experience to new heights. These curtains strike the perfect balance between style and functionality, providing privacy, UV protection, and an added touch of sophistication to your vehicle's interior. Whether you're embarking on a road trip or commuting daily, these curtains will transform your driving space into a more comfortable and stylish haven.
Key Features:
– Custom Fit: Tailored specifically for Mitsubishi Pajero 4th Gen, ensuring a seamless and sleek appearance.
– Privacy & UV Protection: Keep prying eyes out while safeguarding your car's interior from harsh sunlight.
– Easy Installation: Includes an installation kit and step-by-step instructions for hassle-free setup.
– Enhanced Comfort: Control light and visibility according to your preference for a more pleasant ride.
– Durable Material: Built to last and easy to maintain, ensuring long-lasting quality.
Inside the Box:
– Two or four custom-fit curtains with clips
– Four or eight railings with VHB tape
– Two or four or six velcros with VHB Tape
– One alcohol swab tissue
– One 3M™ Tape Primer 94 bottle (Pakistan)
– Two 3M™ Tape Primer 94 Tissue (International)
– One Pouch of 8 Extra Clips & 2 Stoppers
– One extra tape approx. 2 meters
– Easy-to-follow instructions
Elevate your Mitsubishi Pajero 4th Gen with these curtains today, and experience the perfect blend of style and practicality every time you hit the road.


text:
A build system, at its heart, is a system which runs commands in an order satisfying user-specified dependencies. But what kind of dependencies can be expressed? This post describes three different types of dependency, only one of which is available in Make, but all of which are available in both Shake and Ninja.
Feature 1: Static dependencies (available in every build system)
The most basic form of dependency is a static dependency, where a rule produces an output from some inputs:
-- In Make -- result.tar : file1 file2 tar -cf result.tar file1 file2 -- In Shake -- "result.tar" *> \out -> do let deps = ["file1","file2"] need deps cmd "tar -cf" [out] deps
This rule says that the file result.tar depends on the inputs file1 and file2, and provides a command to build result.tar. Whenever file1 or file2 change, the command will be run, and result.tar will be built.
Static dependencies occur in almost every build rule, and are supported by all build tools, including Make and Shake.
Feature 2: Dynamic dependencies (available in Shake, Ninja, Redo and tup)
A more advanced dependency is where the list of dependencies itself depends on the results of previous dependencies. Imagine we want to build result.tar from the list of files stored in list.txt. The dependencies of result.tar cannot be specified statically, but depend on the contents of list.txt. In Shake we can write:
"result.tar" *> \out -> do need ["list.txt"] contents <- readFileLines "list.txt" need contents cmd "tar -cf" [out] contents
This rule describes how to build result.tar. We depend on (need) the file list.txt. We read each line from list.txt into the variable contents - being a list of the files that should go into result.tar. Next, we depend on all the files in contents, and finally call the tar program. If either list.txt changes, or any of the files listed by list.txt change, then result.tar will be rebuilt.
This feature is necessary in almost every build system, yet is shockingly lacking from most build tools - I am only aware of it being available in Shake, Ninja, Redo and tup. As a common example, in Make you might write:
result.o : result.c result_header1.h result_header2.h gcc ...
The file result.o depends on both the C source file result.c and all headers that file includes. But listing the headers both in result.c with #include directives, and in the Makefile, is a brittle form of duplication. A better approach is for the build system to run gcc -M result.c and extract the includes from there. In Shake we can write:
"result.o" *> \out -> do let src = "result.c" Stdout stdout <- cmd "gcc -MM" [src] need $ src : drop 2 (words stdout) cmd "gcc -o" [out] "-c" [src]
My experience is that about a quarter of rules require some kind of additional dependency based on previous dependencies. While you can hack round some of the issues in Make, and people have become disturbingly adept at doing so, the result often only approximates the dependencies - building either too much or too little.
Feature 3: Multiple outputs from one rule (available in Shake and Ninja)
The final feature is producing multiple outputs from one command, and is used far more rarely (perhaps one or two rules in a complex build system) - but when needed, is essential. Some programs, such as GHC, can produce two outputs with one command - compiling Foo.hs produces both Foo.o and Foo.hi. As a first approximation, the .o file depends on the entire contents of the source file, while the .hi file depends only on the type signatures. A single ghc invocation needs to do all the work to produce both, but often the .hi file will be left unchanged. In Shake we can write:
["Foo.hi","Foo.o"] *>> \_ -> do need ["Foo.hs"] cmd "gcc -c Foo.hs"
While it is often possible to construct a series of dependencies to approximate a single rule producing multiple outputs, it only works in some cases, and is brittle. The only build systems I am aware of which support multiple outputs are Shake and Ninja.
Essential features
My standard advice when people ask about writing a build system is "don't". If some existing build system (e.g. ghc --make or Cabal) is capable of building your project, use that instead. Custom build systems are necessary for many complex projects, but many projects are not complex. If you have decided your project is complex, you should use a build tool that can express complex dependencies, both for writing the initial system and to provide the flexibility to make the inevitable changes required.
Looking only at dependency features, I would consider it unwise to start a complex build system using a tool other than Shake or Ninja, or perhaps either Redo or tup (if you accept the absence of multiple outputs from one rule).
Weak dependency specification in build tools, particularly Make, has left its mark on many programs. I recently talked to some OCaml hackers complaining that their tools were not "Make friendly" because they produced multiple output files. I wonder what lengths other tools have gone to in order to cope with weak dependency specification...
Update: The relative power of tup was reported as a comment, and it appears to have the necessary power, but I haven't yet checked. Following further research into Ninja I suspect it may not be as powerful as originally stated and may not have Feature 2, but am not yet sure. Make gained support for multiple outputs after this post was published.


text:
Tony Award-winning musical Once has found a home for its London premiere, according to The Daily Mail. The intimate musical will begin performances in March at the West End's Phoenix Theatre. The theater currently houses the long-running musical Blood Brothers, which ends its run on October 27 after a 24-year run. No casting has been announced at this time.
Helmed by John Tiffany, Once features a book by Enda Walsh, with music and lyrics by Glen Hansard and Marketa Irglova. Set in Dublin, Once is the story of an Irish musician and a Czech immigrant who are drawn together by their shared love of music. Over the course of one week, an unexpected friendship and collaboration evolves into a powerful and complicated love story. Once is based on the Academy Award-winning film of the same name, and originally opened at off-Broadway's New York Theatre Workship in 2011.
The Broadway cast of Once includes Tony winner Steve Kazee, Tony nominee Cristin Milioti, Tony nominee Elizabeth A. Davis, David Abeles, Will Connolly, David Patrick Kelly, Eliza Holland Madore, Anne L. Nathan, Lucas Papaelias, Ripley Sobo, Andy Taylor, Erikka Walsh, Paul Whitty and J. Michael Zygo.


text:
Thursday, July 24, 2008
Jedi Dave
I think I lost the floor in about 2003. I remember the moment. I had dropped a sock to the floor and was reaching down to pick it up. Suddenly it seemed as if the sock were miles and miles away, just out of my grasp. My fingertips struggled to make contact. I knew at that moment that anything that hit the floor was now out of my world entirely.
Luckily I'm not that much of a dropsy kind of person so Joe didn't really notice for about a year that I was having him pick up things for me. "Hey, when was the last time you picked something off the floor?" "Um, maybe 16 or 17 months ago." "Oh." That ended the discussion of that.
But today we went shopping for something I need for the bathroom in the new apartment, a tub grip. It's something we realized we would need after only a couple of days in the new place. We knew they had them stocked at the Home Health Care store here in Barrie (where I'm back teaching for two days) and we headed straight there after work. While there I noticed the floor. I looked up and saw these brightly coloured 'reaches' and made my way over to them.
They had a lavender one as a sample and I found that I could pick up a set of keys from the floor. I spent a bit of time picking up a variety of things in the store and then said, "This is cool."
Joe said simply and quietly, "Very cool."
They had two colours, a drab green and a vibrant yellow. I picked as you can see the vibrant yellow one. Once I got it here to the hotel, I pulled it out and picked up pills from across the way, I kept throwing things onto the floor and retreiving them, I got yelled at when I picked up the hem of Joe's bathrobe and peeked. This thing is awesome. It's kind of like a light saber for crippled guys.
This is the kind of thing that I think the poor non-disabled need to discover. You can use it for so many things, drop something behing the fridge or beside the stove - well this is the ticket.
I am now waiting for the day that a light goes out.
Because it only takes one disabled guy to change a lightbulb.
No joke.
10 comments:
- wendy said...
Okay...just had to laugh at you peeking under Joe's robe. After all this time don't you...um....KNOW what's there! ;-)
- 24 July 2008 at 05:44
I have my mum's old reaching tool ... I mostly use it for retrieving socks and whatnot that fall between the washer and the wall. But my daughter has used it when she was laid up with owies. Yours looks like a much better model!
andrea - 24 July 2008 at 08:41
- Kei said...
Very cool! May the force(ps) be with you, lol.
- 24 July 2008 at 08:58
I NEED this!
I haven't reached the floor in years. - 24 July 2008 at 11:55
- Shan said...
Ha ha ha!! I could totally use one of those for Piper clean-up. Or, on Christmas Day, I could literally lie around and still get the crumpled wrap picked up!
PS: I'm liking the picture thing you're doing. - 24 July 2008 at 12:07
Hey Dave, required piece of equipment when one has their knees replaced. A little hint I learned from my new "senior" friends...by putting a magnet (or duct tape works too!) on the end it is really easy to pick up money...yours and others. So when you're at the mall..... Chris
- 24 July 2008 at 13:15
We use one to pick up and dispose of the gifts of small dead rodents the cats leave at our door.
- 24 July 2008 at 23:50
- FridaWrites said...
That does look better than mine, like it would pick up more. Brand?
- 25 July 2008 at 20:35
- All 4 My Gals said...
You are so )(*&(@# funny! I was totally seeing you throwing everything down on the floor. And Joe's robe, hilarious! You sound like me, and Joe sounds like well...my Joe. LOL
- 26 July 2008 at 21:55
Lots of great things out there to make life easier. Have you discovered the "sock-putter-on'er" yet? A great lil' piece of equipment that enables you to put your own socks on. I had it given to me along with the "grabber" after a hip replacement surgery. It was pretty cool to be able to get myself fully dressed while recovering. You could call any health care store I'm sure or any OT would be able to get one for you.
- 27 July 2008 at 16:12