search for: upend

...t part right now). I don't particularly want to put it >> on the module because of (admittedly pie in the sky) plans of being able to >> compile a module with two target machines at the same time. > > > Wait, what? The DataLayout can't live in the target machine without upending > the layering completely. Every part of the IR optimizer uses it... > Ha. And yet currently some of them are dependent upon subtarget features. I'm separating them out, but making them "ARM" or "X86" or what have you seems to be the best route. -eric

On Mon, Oct 20, 2014 at 9:51 AM, Chris Lattner <clattner at apple.com> wrote: > > On Oct 19, 2014, at 1:22 AM, Chandler Carruth <chandlerc at gmail.com> wrote: > > > I've just wasted a day chasing my tail because of subtleties introduced > to handle the optionality of the DataLayout. I would like to never do this > again. =] > > > > We now have

...either. --- But given what you say about this release just happening to work on 18.04 - makes me think we should absolutely not rely on any future version functioning on 18.04. Correct? We might get lucky or not. And if we don't get lucky, and we need a security patch - well we'll have to upend our install to go to debian or something... Does that summarize things reasonably well? TIA Louis, et al. LPHvBvs> Hi Gregory, >> -----Oorspronkelijk bericht----- >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens >> Gregory Sloop via samba >> Verzonde...

...nk Louis can either. He might find that he no longer has any Ubuntu machines. Nobody can foretell the future, but, from my understanding, Louis plans to provide the debs for the foreseeable future. > > And if we don't get lucky, and we need a security patch - well we'll > have to upend our install to go to debian or something... > > Does that summarize things reasonably well? Yes Rowland

...rly want to put it >>>> on the module because of (admittedly pie in the sky) plans of being able to >>>> compile a module with two target machines at the same time. >>> >>> >>> Wait, what? The DataLayout can't live in the target machine without upending >>> the layering completely. Every part of the IR optimizer uses it... >> >> Ha. And yet currently some of them are dependent upon subtarget >> features. I'm separating them out, but making them "ARM" or "X86" or >> what have you seems to...

So, Louis - I'm quite interested in using your repo for Samba support on 18.04. You note there's some detail on it on the github site - but I don't seem to find it. Also - while I know it's all just best intentions etc - is this something you intend to do for a while? [I'd be glad to toss some $$$ your way to help, if that's helpful. I'd toss some bucks to SerNet - but

...* header length entries to store the header. */ struct iovec hdr[sizeof(struct virtio_net_hdr_mrg_rxbuf)]; size_t vhost_hlen; size_t sock_hlen; struct vring_used_elem *heads; ... /* vhost zerocopy support fields below: */ /* last used idx for outstanding DMA zerocopy buffers */ int upend_idx; /* first used idx for DMA done zerocopy buffers */ int done_idx; /* an array of userspace buffers info */ struct ubuf_info *ubuf_info; /* Reference counting for outstanding ubufs. * Protected by vq mutex. Writers must also take device mutex. */ struct vhost_ubuf_ref *ubufs; 5) Why doe...

...* header length entries to store the header. */ struct iovec hdr[sizeof(struct virtio_net_hdr_mrg_rxbuf)]; size_t vhost_hlen; size_t sock_hlen; struct vring_used_elem *heads; ... /* vhost zerocopy support fields below: */ /* last used idx for outstanding DMA zerocopy buffers */ int upend_idx; /* first used idx for DMA done zerocopy buffers */ int done_idx; /* an array of userspace buffers info */ struct ubuf_info *ubuf_info; /* Reference counting for outstanding ubufs. * Protected by vq mutex. Writers must also take device mutex. */ struct vhost_ubuf_ref *ubufs; 5) Why doe...