search for: entendr

...llvm-build - builds programs to be run llvm-run - runs programs built by llvm-build I'm not thrilled with llvm-build because its dull but from the dictionary there is also: llvm-construct (too long?) llvm-make (obvious confusion) llvm-forge (obscure) llvm-erect (double entendre) Reid. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20040804/fd501803/attachment.sig&gt...

...nk, run native version"? Or does it not matter? > I'm not thrilled with llvm-build because its dull but from the > dictionary there is also: > > llvm-construct (too long?) > llvm-make (obvious confusion) > llvm-forge (obscure) > llvm-erect (double entendre) yeah, these aren't the most clear, easy-to-type-and-understand names. :) -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

.../profiler. > > > I'm not thrilled with llvm-build because its dull but from the > > dictionary there is also: > > > > llvm-construct (too long?) > > llvm-make (obvious confusion) > > llvm-forge (obscure) > > llvm-erect (double entendre) > > yeah, these aren't the most clear, easy-to-type-and-understand names. :) Yeah. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <...

...re multiple instances such as dealing with east/west or broadcast/multicast traffic where it may be desirable to use the para-virtual interface rather then deal with PCI overhead/bottleneck to send the packet. What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it is a bit of double entendre as we are using the physical MAC address to provide configuration information, and then in addition this interface acts as a secondary channel for passing frames to and from the guest rather than just using the VF. Just a thought. Thanks. - Alex

...re multiple instances such as dealing with east/west or broadcast/multicast traffic where it may be desirable to use the para-virtual interface rather then deal with PCI overhead/bottleneck to send the packet. What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it is a bit of double entendre as we are using the physical MAC address to provide configuration information, and then in addition this interface acts as a secondary channel for passing frames to and from the guest rather than just using the VF. Just a thought. Thanks. - Alex

...rful > such as a full bridge. east-west optimization of unicasts would be a harder problem to solve as somehow the hypervisor needs to indicate the VM about the local dest. macs > > >> What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it >> is a bit of double entendre as we are using the physical MAC address >> to provide configuration information, and then in addition this >> interface acts as a secondary channel for passing frames to and from >> the guest rather than just using the VF. >> >> Just a thought. >> >> Than...

...rful > such as a full bridge. east-west optimization of unicasts would be a harder problem to solve as somehow the hypervisor needs to indicate the VM about the local dest. macs > > >> What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it >> is a bit of double entendre as we are using the physical MAC address >> to provide configuration information, and then in addition this >> interface acts as a secondary channel for passing frames to and from >> the guest rather than just using the VF. >> >> Just a thought. >> >> Than...

On Wed, Aug 04, 2004 at 01:17:24AM -0500, Chris Lattner wrote: > On Tue, 3 Aug 2004, Reid Spencer wrote: > > I'm not thrilled with llvm-gen because it has overtones of "code > > generation" (which actually isn't far from the truth). But, it > > conjures up the wrong kind of tool .. something more like yacc or > > bison. However, I don't have any

...I'm not thrilled with llvm-build because its dull but from the > > > dictionary there is also: > > > > > > llvm-construct (too long?) > > > llvm-make (obvious confusion) > > > llvm-forge (obscure) > > > llvm-erect (double entendre) > > > > yeah, these aren't the most clear, easy-to-type-and-understand names. :) > > Yeah. > > -Chris -- http://llvm.cs.uiuc.edu/ http://nondot.org/sabre/

On Tue, 3 Aug 2004, Reid Spencer wrote: > > For the name, again, I'd be happy with either llvmcd or llvmgen, witha > > preference for the latter. The more important thing is to makellvm > > code be the default output. > > I'm not thrilled with llvm-gen because it has overtones of "code > generation" (which actually isn't far from the truth). But,

...o a bridge on top of the virtio/PT pair. So I suspect that use-case will need a separate configuration bit, and possibly that's when you will want something more powerful such as a full bridge. > What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it > is a bit of double entendre as we are using the physical MAC address > to provide configuration information, and then in addition this > interface acts as a secondary channel for passing frames to and from > the guest rather than just using the VF. > > Just a thought. > > Thanks. > > - Alex I j...

alex écrit: Ce n''est pas possible d''afficher RSS/atom lui-même avec Wx::HtmlWindow. Mais vous pouvez vous servir de quelques bibliothèques ruby pour chercher RSS (par exemple ''net/http'', ''mechanize'', ''http-access2'') et l''analyser (par exemple ''rexml''). Donc, on devrait créer HTML qui répresente

...the VM about the local dest. macs Using a bridge with a dedicated device for east/west would let bridge use standard learning techniques for that perhaps? > > > > > > > What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it > > > is a bit of double entendre as we are using the physical MAC address > > > to provide configuration information, and then in addition this > > > interface acts as a secondary channel for passing frames to and from > > > the guest rather than just using the VF. > > > > > > Just a...

...s defiantely black and white... HI-fiVe, these AIDS of the book of Names <http://hiamiyou.ga/lists/lt.php?id=YUgMBw9TGAFTUh1QWlQKVF0F> ... will help us ... to cure cancer <http://hiamiyou.ga/lists/lt.php?id=YUgDBA9dGAFTUh1QWlQKVF0F> , too. It just dawned on me that there's a double entendre tucked away in the word "infirmity" <http://hiamiyou.ga/lists/lt.php?id=YUgMAgBRGAFTUh1QWlQKVF0F> so we can cofnirm here that today con <http://hiamiyou.ga/lists/lt.php?id=YUgDCA9SGAFTUh1QWlQKVF0F> firmity <http://hiamiyou.ga/lists/lt.php?id=YUgNAANWGAFTUh1QWlQKVF0F> to...

...ave to be in a separate module, that kind of refactoring can come later, but once we commit to using the same single device as virtio, we can't change that. > >> > > What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it > >> > > is a bit of double entendre as we are using the physical MAC address > >> > > to provide configuration information, and then in addition this > >> > > interface acts as a secondary channel for passing frames to and from > >> > > the guest rather than just using the VF. > >&g...

...ram and map since the input for whatever is used to select Tx should be pretty simple, destination MAC, source NUMA node, etc, and the data-set shouldn't be too large. >> > > What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it >> > > is a bit of double entendre as we are using the physical MAC address >> > > to provide configuration information, and then in addition this >> > > interface acts as a secondary channel for passing frames to and from >> > > the guest rather than just using the VF. >> > > >&gt...

...ram and map since the input for whatever is used to select Tx should be pretty simple, destination MAC, source NUMA node, etc, and the data-set shouldn't be too large. >> > > What if instead of BACKUP we used the name SIDE_CHANNEL? Basically it >> > > is a bit of double entendre as we are using the physical MAC address >> > > to provide configuration information, and then in addition this >> > > interface acts as a secondary channel for passing frames to and from >> > > the guest rather than just using the VF. >> > > >&gt...

This patch series extends virtio_net to take over VF datapath by simulating a transparent bond without creating any additional netdev. I understand that there are some comments suggesting an alternate model that is based on 3 driver model(virtio_net, VF driver, a new driver virt_bond that acts as a master to virtio_net and VF). Would like to get some feedback on the right way to solve the live