search for: then

...ct it. 'ip link' is the right place. I agree on this. What I really don't understand still is the use case... really. So there are control netdevs, what exactly is the problem with that? Are we not exporting enough information for applications to handle these devices sanely? If so, then's let add that information. We can set netdev->type to ETH_P_LINUXCONTROL or something like that. Another alternative is to add an interface flag like IFF_CONTROL or similar, and that probably is much nicer. Hiding the devices means that we acknowledge that applications are currently brok...

...ct it. 'ip link' is the right place. I agree on this. What I really don't understand still is the use case... really. So there are control netdevs, what exactly is the problem with that? Are we not exporting enough information for applications to handle these devices sanely? If so, then's let add that information. We can set netdev->type to ETH_P_LINUXCONTROL or something like that. Another alternative is to add an interface flag like IFF_CONTROL or similar, and that probably is much nicer. Hiding the devices means that we acknowledge that applications are currently brok...

...let me know. Thanks, -Siwei > > What I really don't understand still is the use case... really. > > So there are control netdevs, what exactly is the problem with that? > > Are we not exporting enough information for applications to handle > these devices sanely? If so, then's let add that information. > > We can set netdev->type to ETH_P_LINUXCONTROL or something like that. > > Another alternative is to add an interface flag like IFF_CONTROL or > similar, and that probably is much nicer. > > Hiding the devices means that we acknowledge that...

...t set up with developer tools, you are packaging the static library inside a DLL/DSO. In addition, with all the minor variations of GPUs, having a separate archive for every GPU type would be too large, so you need some way to remove duplicates of support functions. If the above summary is close, then here are two other ideas that avoid the need for archive/TOC changes: 1) Have lots of little archives which removes duplicates. Give each archive a unique name, then have a lookup table which lists which sequence of archives to use for which specific GPU. When linking for a particular GPU, you pa...

I've been looking at the --progress reporting, which is somewhat improved these days. But look at this output of this evening rawhide mirror update: [...] perl-DB_File-1.75-27.i386.rpm 73430 100% 519.63kB/s 0:00:00 perl-DB_File-1.75-28.99.3.i386.rpm 61783 100% 533.94kB/s 0:00:00 [...] Now, while it's good to have the ETA ticking down as something is fetched,

The time has come to expand my OpenSolaris NAS. Right now I have 6 1TB Samsung Spinpoints in a Raidz2 configuration. I also have a mirrored root pool. The Raidz2 configuration should be for my most critical data - but right now it is holding everything so I need to add some more pools and move some data around. To start I need a vdev I will call "temp" that acts as a networked bit

.... This is making the loop more complicated, not simple, and is causing our backend to miss performance opportunities. In particular, I have the following loop: While (n) { If (c) A Else B } Normally I would expect to rotate the loop termination test to the end of the loop, and then our backend would if-convert blocks A and B and then effectively software pipeline the entire loop. However, because the loop has two backedges (from A and from B), the LoopSimplify pass will create a nested loop, which I awkwardly write in C as: While (n) { While (n) { If (c)...

...also will enhance ranlib to accept multiple archive names on the command line and produce the "super-archive" from ranlib. A further need we have is to serialize the TOCs and the super-archive in a memory image (our archives are embedded in our DLL/SO, not stored separately on disk) and then provide an interface to the relevant LLVM classes (Linker, primarily) for accessing archives in memory rather than on disk, a feature absent from the current implementation. For our purposes, extending the Archive class to support specification of the archive using a memory object instead of a fil...

I''m using puppet 0.25.1. I''ve got a simple resource: exec { "/bin/ls $oracle_base/dba/bin/database_backup.ksh": logoutput => on_failure, } and I don''t want it to log every time it''s successfully run: $ sudo tail -F /var/log/messages | grep puppetd Feb 17 16:36:11 test puppetd[26614]: (//my_module/Exec[/bin/ls /u01/

On 10/18/2012 01:26 PM, David Blaikie wrote: > On Thu, Oct 18, 2012 at 10:12 AM, Andrew Clinton<andrew at sidefx.com> wrote: >> I actually submitted a patch to fix this very problem quite a while back, >> but I don't think it was ever added to the baseline: >> >> http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20110711/124136.html >> >>

...ustomer form collecting name, and email. In the context of the wizard I feel that the following scenarios Scenario: Given I step to customer And I fill in my customer details correctly Scenario: Given I step to customer And I fill in my customer details incorrectly Then I should see an error are preferable to Scenario: Given I step to customer And I fill in email with fred at example.com And I fill in name "Fred Bloggs" Given I step to customer And I fill in email with '''' And I fill in name &quot...

...oo large, so you need some way to remove duplicates of support functions. Close. But it isn't "support routines". It's the entire OpenCL "built-in" library… thousands and thousands of functions, some tiny, some large, some merely aliases. If the above summary is close, then here are two other ideas that avoid the need for archive/TOC changes: 1) Have lots of little archives which removes duplicates. Give each archive a unique name, then have a lookup table which lists which sequence of archives to use for which specific GPU. When linking for a particular GPU, you pa...

Hi all, I committed a first cut at blockless Givens/Whens/Thens to RSpec''s trunk: cd /path/to/rspec/project svn up cd rspec bin/spec examples/story/calculator.rb Take a look at examples/story/calculator.rb to see what''s going on. Needs docs!!!! Thoughts welcome. I''ve also got a cut at the plain text parser checked in, but it'...

I'm coming from a Debian system so my system accounts are below 1000, regular accounts start at 1000. For some historical reason somebody gave our main group id 500 so therefor I want my usable range to start at 500. Do I need both idmap config *:range and idmap config SAMDOM:range? I also tried with only 'idmap config *:range' but that didn't seem to help. I'll try again

hi, I just started fooling around with story runner, thought I''d start with a dead simple scenario: The first thing I do when describing a site to someone is go to the home page, and begin exploring public pages from there. So, that seems like a good first story to spec out. And I''d really like to extract the actual link from the rendered page (rather than just