os161中的UIO_USERISPACE,UIO_USERSPACE和UIO_SYSSPACE是什么?

如何解决os161中的UIO_USERISPACE,UIO_USERSPACE和UIO_SYSSPACE是什么?

我正在尝试完成操作系统课程Here的作业。

我对作业有疑问:

UIO_USERISPACE和UIO_USERSPACE有什么区别?什么时候应该使用UIO_SYSSPACE代替?

当我在源代码中搜索here时,我发现了这一点:

/* Source/destination. */
enum uio_seg {
        UIO_USERISPACE,/* User process code. */
        UIO_USERSPACE,/* User process data. */
        UIO_SYSSPACE,/* Kernel. */
};

struct uio {
    struct iovec     *uio_iov;  /* Data blocks */
    unsigned          uio_iovcnt;   /* Number of iovecs */
    off_t             uio_offset;   /* Desired offset into object */
    size_t            uio_resid;    /* Remaining amt of data to xfer */
    enum uio_seg      uio_segflg;   /* What kind of pointer we have */
    enum uio_rw       uio_rw;   /* Whether op is a read or write */
    struct addrspace *uio_space;    /* Address space for user pointer */
};

我可以看到它在结构uio中使用(我将在另一个问题中对此进行询问)以指示“使用了哪种指针”。

此外,我可以在函数uiomovehere的描述中看到它:

 *   (5) if uio_seg is UIO_SYSSPACE,set uio_space to NULL; otherwise,*       initialize uio_space to the address space in which the buffer
 *       should be found.

函数uiomovehere的完整说明:

/*
 * Copy data from a kernel buffer to a data region defined by a uio struct,* updating the uio struct's offset and resid fields. May alter the iovec
 * fields as well.
 *
 * Before calling this,you should
 *   (1) set up uio_iov to point to the buffer(s) you want to transfer
 *       to,and set uio_iovcnt to the number of such buffers;
 *   (2) initialize uio_offset as desired;
 *   (3) initialize uio_resid to the total amount of data that can be
 *       transferred through this uio;
 *   (4) set up uio_seg and uio_rw correctly;
 *   (5) if uio_seg is UIO_SYSSPACE,*       initialize uio_space to the address space in which the buffer
 *       should be found.
 *
 * After calling,*   (1) the contents of uio_iov and uio_iovcnt may be altered and
 *       should not be interpreted;
 *   (2) uio_offset will have been incremented by the amount transferred;
 *   (3) uio_resid will have been decremented by the amount transferred;
 *   (4) uio_segflg,uio_rw,and uio_space will be unchanged.
 *
 * uiomove() may be called repeatedly on the same uio to transfer
 * additional data until the available buffer space the uio refers to
 * is exhausted.
 *
 * Note that the actual value of uio_offset is not interpreted. It is
 * provided (and updated by uiomove) to allow for easier file seek
 * pointer management.
 *
 * When uiomove is called,the address space presently in context must
 * be the same as the one recorded in uio_space. This is an important
 * sanity check if I/O has been queued.
 */

函数uiomovehere的定义:

int
uiomove(void *ptr,size_t n,struct uio *uio)
{
    struct iovec *iov;
    size_t size;
    int result;

    if (uio->uio_rw != UIO_READ && uio->uio_rw != UIO_WRITE) {
        panic("uiomove: Invalid uio_rw %d\n",(int) uio->uio_rw);
    }
    if (uio->uio_segflg==UIO_SYSSPACE) {
        KASSERT(uio->uio_space == NULL);
    }
    else {
        KASSERT(uio->uio_space == proc_getas());
    }

    while (n > 0 && uio->uio_resid > 0) {
        /* get the first iovec */
        iov = uio->uio_iov;
        size = iov->iov_len;

        if (size > n) {
            size = n;
        }

        if (size == 0) {
            /* move to the next iovec and try again */
            uio->uio_iov++;
            uio->uio_iovcnt--;
            if (uio->uio_iovcnt == 0) {
                /*
                 * This should only happen if you set
                 * uio_resid incorrectly (to more than
                 * the total length of buffers the uio
                 * points to).
                 */
                panic("uiomove: ran out of buffers\n");
            }
            continue;
        }

        switch (uio->uio_segflg) {
            case UIO_SYSSPACE:
                if (uio->uio_rw == UIO_READ) {
                    memmove(iov->iov_kbase,ptr,size);
                }
                else {
                    memmove(ptr,iov->iov_kbase,size);
                }
                iov->iov_kbase = ((char *)iov->iov_kbase+size);
                break;
            case UIO_USERSPACE:
            case UIO_USERISPACE:
                if (uio->uio_rw == UIO_READ) {
                    result = copyout(ptr,iov->iov_ubase,size);
                }
                else {
                    result = copyin(iov->iov_ubase,size);
                }
                if (result) {
                    return result;
                }
                iov->iov_ubase += size;
                break;
            default:
                panic("uiomove: Invalid uio_segflg %d\n",(int)uio->uio_segflg);
        }

        iov->iov_len -= size;
        uio->uio_resid -= size;
        uio->uio_offset += size;
        ptr = ((char *)ptr + size);
        n -= size;
    }

    return 0;
}

我似乎不赞成使用它。谁能给我一些关于他们的直觉?例如,何时何地使用它们?他们的目的是什么?而且,对于原始问题的答案,UIO_USERISPACEUIO_USERSPACE有什么区别?什么时候应该使用UIO_SYSSPACE代替?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-