Поиск по:jet.sao.ru -
Поискать по всем серверам
На этой странице приведены все страницы сервера jet.sao.ru ,которые мы индексируем. Показаны документы 1981 - 2000 из 5951.
Упорядочить по:
URL
|
дате изменения
1981. LWN: Driver porting: Request Queues I
... This article is part of the LWN Porting Drivers to 2.5 series . The simple block driver example earlier in this series showed how to write the simplest possible request function. ... This article will get into the details of how request queues work, with an emphasis on what every driver writer needs to know to process requests. ... Request queues are represented by a pointer to struct request_queue or to the typedef request_queue_t , defined in <linux/blkdev.h> . ... Request clustering control . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/27055.html -- 24.3 Кб -- 02.10.2012
Похожие документы
Похожие документы
1982. LWN: Driver porting: the BIO structure
... This article is part of the LWN Porting Drivers to 2.6 series . The block layer in 2.4 (and prior) kernels was organized around the buffer head data structure. ... The result was the new BIO structure. ... The BIO structure itself contains the usual collection of housekeeping information, along with a pointer ( bi_io_vec ) pointing to an array of bio_vec structures. ... As is increasingly the case with internal kernel data structures, the BIO now tracks data buffers using struct page pointers. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/26404.html -- 22.4 Кб -- 02.10.2012
Похожие документы
Похожие документы
1983. LWN: Driver porting: the gendisk interface
... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . The 2.4 kernel gendisk structure is used almost as an afterthought; its main purpose is to help in keeping track of disk partitions. ... This article will cover the details of the gendisk structure from a disk driver's perspective. ... If your driver makes a disk (or disk-like) device available to the system, it will have to provide an associated gendisk structure. ... After this call, your device is active. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/25711.html -- 21.0 Кб -- 02.10.2012
Похожие документы
Похожие документы
1984. LWN: Driver Porting: block layer overview
... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . The first big, disruptive changes to the 2.6 kernel came from the reworking of the block I/O layer. ... Buffer heads are no longer used in the block layer; they have been replaced with the new " bio " structure. ... The most significant change for block driver authors, though, may be the fact that partition handling has been moved up into the block layer, and drivers no longer need know anything about partitions. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/24990.html -- 14.5 Кб -- 02.10.2012
Похожие документы
Похожие документы
1985. LWN: Driver porting: supporting asynchronous I/O
... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . ... Block and network drivers are already fully asynchronous, and thus there is nothing special that needs to be done to them to support the new asynchronous operations. ... ssize_t (*aio_read) (struct kiocb *iocb, char __user *buffer, size_t count, loff_t pos); ssize_t (*aio_write) (struct kiocb *iocb, const char __user *buffer, size_t count, loff_t pos); int (*aio_fsync) (struct kiocb *, int datasync); . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/24366.html -- 17.5 Кб -- 02.10.2012
Похожие документы
Похожие документы
1986. LWN: Driver porting: completion events
... LWN.net Weekly Edition for March 18, 2004 . ... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . Completions are a simple synchronization mechanism that is preferable to sleeping and waking up in some situations. ... When your driver begins some process whose completion must be waited for, it's simply a matter of passing your completion event to wait_for_completion() : . ... void complete(struct completion *comp); void complete_all(struct completion *comp); . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/23993.html -- 11.9 Кб -- 02.10.2012
Похожие документы
Похожие документы
1987. LWN: Driver porting: the workqueue interface.
... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . The longstanding task queue interface was removed in 2.5.41; in its place is a new "workqueue" mechanism. ... Tasks to be run out of a workqueue need to be packaged in a struct work_struct structure. ... INIT_WORK must be used at least once before queueing the work_struct structure, but should not be used if the work_struct might already be in a workqueue. ... Driver porting: the workqueue interface. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/23634.html -- 16.5 Кб -- 02.10.2012
Похожие документы
Похожие документы
1988. LWN: Driver porting: dealing with interrupts
... Kernel . ... This article is part of the LWN Porting Drivers to 2.6 series . The kernel's handling of device interrupts has been massively reworked in the 2.6 series. ... If no interrupt handler for a given IRQ has been registered, the kernel knows that any interrupt on that number is spurious. ... If your interrupt handler recognizes and handles a given interrupt, it should return IRQ_HANDLED . ... can also be used; handled should be nonzero if the handler could deal with the interrupt. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/23625.html -- 14.6 Кб -- 02.10.2012
Похожие документы
Похожие документы
1989. LWN: Driver porting: sleeping and waking up
... Return to the Kernel page . ... Kernel . ... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . ... In many situations, one can use the wait_event() macros: . DECLARE_WAIT_QUEUE_HEAD(queue); wait_event(queue, condition); int wait_event_interruptible (queue, condition); . ... Each wait queue entry now includes its own "wake function," whose job it is to handle wakeups. ... Driver porting: sleeping and waking up . ... Driver porting: wait queue and preemptible code . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22913.html -- 22.2 Кб -- 02.10.2012
Похожие документы
Похожие документы
1990. LWN: Driver porting: the preemptible kernel
... LWN.net Weekly Edition for March 18, 2004 . ... Kernel . ... LWN.net FAQ . ... This article is part of the LWN Porting Drivers to 2.6 series . One significant change introduced in 2.6 is the preemptible kernel. ... In 2.6, if preemption is configured in, kernel code can be interrupted at (almost) any time. ... The preemptible kernel means that your driver code can be preempted whenever the scheduler decides there is something more important to do. ... Driver porting: the preemptible kernel . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22912.html -- 14.4 Кб -- 02.10.2012
Похожие документы
Похожие документы
1991. LWN: Driver porting: per-CPU variables
... Return to the Kernel page . ... This article is part of the LWN Porting Drivers to 2.6 series . The 2.6 kernel makes extensive use of per-CPU data - arrays containing one object for each processor on the system. Per-CPU variables are not suitable for every task, but, in situations where they can be used, they do offer a couple of advantages: . Per-CPU variables have fewer locking requirements since they are (normally) only accessed by a single processor. ... DEFINE_PER_CPU(type, name); . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22911.html -- 14.2 Кб -- 02.10.2012
Похожие документы
Похожие документы
1992. LWN: Driver porting: low-level memory allocation
Summary page . Return to the Kernel page . ... This article is part of the LWN Porting Drivers to 2.6 series . The 2.5 development series has brought relatively few changes to the way device drivers will allocate and manage memory. ... GFP_HIGHUSER : for allocating user-space pages where high memory may be used. ... struct page *alloc_pages_node(int node_id, unsigned int gfp_mask, unsigned int order); . ... void free_hot_page(struct page *page); void free_cold_page(struct page *page); . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22909.html -- 17.7 Кб -- 02.10.2012
Похожие документы
Похожие документы
1993. LWN: Driver porting: mutual exclusion with seqlocks
... LWN.net FAQ . ... Write for LWN . ... This article is part of the LWN Porting Drivers to 2.6 series . ... void write_seqlock( seqlock_t *sl); void write_sequnlock( seqlock_t *sl); int write_tryseqlock( seqlock_t *sl); void write_seqlock_irqsave( seqlock_t *sl, long flags); void write_sequnlock_irqrestore( seqlock_t *sl, long flags); void write_seqlock_irq( seqlock_t *sl); void write_sequnlock_irq( seqlock_t *sl); void write_seqlock_bh( seqlock_t *sl); void write_sequnlock_bh...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22818.html -- 13.7 Кб -- 02.10.2012
Похожие документы
Похожие документы
1994. LWN: Driver porting: Timekeeping changes
... Return to the Kernel page . ... Kernel . ... This article is part of the LWN Porting Drivers to 2.6 series . One might be tempted to think that the basic task of keeping track of the time would not change that much from one kernel to the next. ... One change which shouldn't be problematic for most code is the change in the internal clock rate on the x86 architecture. In previous kernels, HZ was 100; in 2.6 it has been bumped up to 1000. ... Driver porting: Timekeeping changes . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22808.html -- 16.4 Кб -- 02.10.2012
Похожие документы
Похожие документы
1995. LWN: Driver porting: The seq_file interface
... This article is part of the LWN Porting Drivers to 2.6 series . ... Handling multiple reads (and seeks) requires careful attention to the reader's position within the virtual file - that position is, likely as not, in the middle of a line of output. ... This interface (called "seq_file") is not strictly a 2.6 feature - it was also merged into 2.4.15. ... The seq_file interface is available via <linux/seq_file.h> . There are three aspects to seq_file: . ... Driver porting: The seq_file interface . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22355.html -- 29.2 Кб -- 02.10.2012
Похожие документы
Похожие документы
1996. LWN: Driver porting: more module changes
... Kernel . ... This article is part of the LWN Porting Drivers to 2.6 series . The first article in this series noted a couple of changes that result from the new, kernel-based module loader. ... Parameters are then declared with module_param : module_param(name, type, perm); Where name is the name of the parameter (and of the variable holding its value), type is its type, and perm is the permissions to be applied to that parameter's sysfs entry. ... Driver porting: more module changes . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22197.html -- 25.2 Кб -- 02.10.2012
Похожие документы
Похожие документы
1997. LWN: Driver porting: miscellaneous changes
... This article is part of the LWN Porting Drivers to 2.6 series . This article serves as a sort of final resting place for various small changes in the kernel programming API which do not fit elsewhere. The kdev_t type has been removed from the kernel; everything which works with device numbers should now use the dev_t type. ... Consider using these while fixing your code; the next time the type of i_rdev changes, you will be happier. ... Driver porting: miscellaneous changes, designated inits . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/22196.html -- 16.0 Кб -- 02.10.2012
Похожие документы
Похожие документы
1998. LWN: Driver porting: compiling external modules
... This article is part of the LWN Porting Drivers to 2.6 series . The 2.5 development series saw extensive changes to the kernel build mechanism and the complete replacement of the module loading code. ... You also, however, need a configured kernel source tree and a set of makefile rules describing how modules are built. ... So, now that you are convinced that you want to use the kernel build system for external modules, how is that to be done? ... Driver porting: compiling external modules . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/21823.html -- 35.1 Кб -- 02.10.2012
Похожие документы
Похожие документы
1999. LWN: Driver porting: hello world
... Kernel . ... This article is part of the LWN Porting Drivers to 2.6 series . ... The obvious place to start in this sort of exercise, of course, is the classic "hello world" program, which, in this context, is implemented as a kernel module. The 2.4 version of this module looked like: #define MODULE #include <linux/module.h> #include <linux/kernel.h> int init_module(void) { printk(KERN_INFO "Hello, world\n"); return 0; } void cleanup_module(void) { printk(KERN_INFO "Goodbye cruel world\n"); } . ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/porting_to_26/21817.html -- 14.4 Кб -- 02.10.2012
Похожие документы
Похожие документы
2000. More IPC Resources
Here are some books that describe some of the procedures I've discussed in this guide, as well as Unix details in specific: . Bach, Maurice J. The Design of the UNIX Operating System . New Jersey: Prentice-Hall, 1986. ISBN 0-13-201799-7. Stevens, Richard W. UNIX Network Programming . New Jersey: Prentice-Hall, 1990. ... For online ordering, try Amazon Books or Computer Literacy Bookshops (my personal favorite computer bookstore). ... ipcs . ... Copyright 1997 by Brian "Beej" Hall. ...
[
Сохраненная копия
]
Ссылки http://jet.sao.ru/hq/sts/linux/doc/ipc_guide/resources.html -- 6.5 Кб -- 02.10.2012
Похожие документы
Похожие документы