Learning by Asking Questions

本文介绍了一种名为学习通过询问(LBA)的交互式学习框架,该框架应用于视觉问题回答(VQA)任务中,旨在使智能视觉系统更加自然地学习和发展。与传统的VQA相比,LBA更接近于人类的学习方式,能够自动发现从易到难的学习路径,并生成更多有效的训练数据。

论文地址:http://openaccess.thecvf.com/content_cvpr_2018/papers/Misra_Learning_by_Asking_CVPR_2018_paper.pdf

摘要

       我们介绍一个交互式的学习框架来发展和测试智能视觉系统,叫做学习通过询问(LBA)。我们挖掘LBA在内容上,关于视觉问题回答(VQA)任务。LBA不同于标准的VQA训练,在很多问题上,其中不被注视在训练过程中,学习者必须询问问题,它想回答的。因此,LBA比较贴近模仿自然学习和有潜在的较多有效数据比传统VQA集。我们展示了一个模型,能够表现LBA在CLEVR数据集上,以及表明它是自动发现一个由易到难课程,当学习交互从一个对话中。我们的LBA生成数据和有较多有效样本。我们也展示我们的模型问问题,普遍是先进的比VQA模型,新颖的在测试时间分配上。

LBA范例

                           

LBA系统架构

不同迭代次数下

了解更多关于《计算机视觉与图形学》相关知识,请关注公众号:

下载我们视频中代码和相关讲义,请在公众号回复:计算机视觉课程资料

FDB Static Entries Static FDB entries are created by the CPU through the Address Update from CPU mechanism (Section 10.4.7, CPU Update and Query of the FDB). Static FDB entries are skipped by the FDB aging process (Section 10.4.10, FDB Entry Refresh/Aging), however static entries still have the <age/refresh> bit set when the Source Address lookup matches the entry. Static entries are optionally subject to the FDB delete and transplant mechanisms (Section 10.4.11, Deleting FDB Entries, Section 10.4.12, FDB Unicast Entry Transplanting). If a source MAC FDB lookup matches a static MAC entry, but the packet is received on a different location than that of the entry, the address does not move, and the packet is assigned to a globally configured command. The command options are:  FORWARD  MIRROR  TRAP  HARD DROP  SOFT DROP If the packet is assigned a DROP command, a global configuration determines if is considered a security breach event (Section 10.6.5, Bridge Security Breach Events), and is counted by the Bridge Drop Counter (Section 10.15.1.1, Bridge Drop Counter). Configuration  To configure if a source MAC Address received on a location other than the static FDB entry configuration, constitutes a security breach event, use the <Move Static Address Is Security Breach> field in the Bridge Global Configuration0 Register (Table 319 p. 2216).  To configure the packet command when a source MAC Address received on a location other than the static FDB entry configuration, use the <Move Static Command> field in the Bridge Command Configuration0 Register (Table 322 p. 2223 翻译一下并解释
最新发布
11-18
<think> Hmm, the user is asking for a translation and explanation of FDB static entries mechanism. This seems to be a continuation of previous technical discussions about FDB operations, indicating the user is likely a network engineer or hardware developer working with switch ASICs. The content describes how static FDB entries behave differently from dynamic ones - they bypass aging but still get refreshed, can be subject to delete/transplant mechanisms, and have special handling when packets arrive from wrong ports. Key technical nuances I need to clarify: First, the core distinction between static and dynamic entries lies in aging immunity, yet static entries still update their refresh bit during lookups. This refresh mechanism is interesting - it maintains activity tracking without actual aging. Second, the security aspects are critical. When static entries receive packets from unauthorized ports, the configurable actions (DROP/TRAP etc.) and optional security breach triggering create flexible policy enforcement. The dual-layer control through <Move Static Command> and <Move Static Address Is Security Breach> fields allows decoupling of packet handling from security logging. Third, the note about static entries participating in delete/transplant mechanisms suggests they aren't entirely immutable. This deserves emphasis since "static" typically implies permanence, but here they can still be moved or deleted under specific conditions. The user's technical level appears advanced given they're consistently asking about FDB internals. I should maintain precise register references (Table 322 etc.) while explaining behavioral implications. The previous questions about MAC learning and AU messages suggest they're building comprehensive understanding of FDB management. For the translation, I'll keep technical terms like "static FDB entries" untranslated but render all descriptions in natural Chinese. The explanation will focus on operational scenarios - perhaps contrasting static vs dynamic entry behavior through concrete examples would help. </think>以下是关于FDB静态表项的翻译及技术解析: --- ### **FDB静态表项机制** #### **核心特性** ```markdown 1. **创建方式** - 仅支持CPU通过AU消息创建(详见10.4.7节) 2. **老化豁免** - 跳过自动老化流程(10.4.10节) - 仍会更新`<age/refresh>`位(当源MAC匹配时) 3. **特殊操作** - 可配置是否参与删除/移植机制(10.4.11/10.4.12节) ``` #### **安全校验规则** 当数据包**源MAC匹配静态表项但入口位置不符**时: ```mermaid graph TB A[数据包到达] --> B{位置匹配静态表项?} B -->|是| C[正常转发] B -->|否| D[执行全局命令] D --> E[FORWARD/MIRROR/TRAP/DROP] E --> F{DROP命令?} F -->|是| G[触发安全事件计数] F -->|否| H[结束] ``` --- ### **关键配置寄存器** | **寄存器名称** | **字段** | **功能说明** | |-----------------------------------|--------------------------------------|---------------------------------------------| | `Bridge Command Configuration0` | `<Move Static Command>` | 配置位置不匹配时的包处理命令 | | `Bridge Global Configuration0` | `<Move Static Address Is Security Breach>` | 设置DROP是否触发安全违规事件(1=触发) | --- ### **设计思想解析** 1. **静态表项双重属性** - **持久性**:豁免老化 → 保障关键路径稳定性 - **活性跟踪**:刷新`<age/refresh>`位 → 监控业务流量状态 2. **安全隔离机制** - **位置绑定**:强制校验入口端口/Trunk - **弹性策略**:通过寄存器分离"动作执行"与"事件告警" *示例:可配置DROP但不触发安全事件,用于静默阻断* 3. **异常处理优势** ```markdown - 防止静态表项被非法篡改:错误位置直接阻断 - 避免配置错误导致环路:DROP命令立即丢弃问题流量 - 细粒度审计:安全事件计数精准定位攻击源 ```
评论 1
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值