search for: newcodes

I'm using a somewhat complicated --include/exclude chain to copy all files matching a pattern, plus all files in certain subdirs. /usr/local/bin/rsync -a --include='*/' --include='*.[wip]' --include='*.htm' --include='*.html' --include='*.off' --include='wwwroot/*' --include='perl/*' --exclude='*' newcode/

On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: > The idea is to support multiple ring formats by converting > to a format-independent array of descriptors. > > This costs extra cycles, but we gain in ability > to fetch a batch of descriptors in one go, which > is good for code cache locality. > > To simplify benchmarking, I kept the old code > around so one can switch

On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: > The idea is to support multiple ring formats by converting > to a format-independent array of descriptors. > > This costs extra cycles, but we gain in ability > to fetch a batch of descriptors in one go, which > is good for code cache locality. > > To simplify benchmarking, I kept the old code > around so one can switch

On 2019/10/13 ??4:27, Michael S. Tsirkin wrote: > On Sat, Oct 12, 2019 at 03:28:49PM +0800, Jason Wang wrote: >> On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: >>> The idea is to support multiple ring formats by converting >>> to a format-independent array of descriptors. >>> >>> This costs extra cycles, but we gain in ability >>> to fetch a

On 2019/10/13 ??4:27, Michael S. Tsirkin wrote: > On Sat, Oct 12, 2019 at 03:28:49PM +0800, Jason Wang wrote: >> On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: >>> The idea is to support multiple ring formats by converting >>> to a format-independent array of descriptors. >>> >>> This costs extra cycles, but we gain in ability >>> to fetch a

This adds infrastructure required for supporting multiple ring formats. The idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will also allow all kind of batching tricks - e.g. it seems possible to keep SMAP disabled while

This adds infrastructure required for supporting multiple ring formats. The idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will also allow all kind of batching tricks - e.g. it seems possible to keep SMAP disabled while

On Sat, Oct 12, 2019 at 03:28:49PM +0800, Jason Wang wrote: > > On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: > > The idea is to support multiple ring formats by converting > > to a format-independent array of descriptors. > > > > This costs extra cycles, but we gain in ability > > to fetch a batch of descriptors in one go, which > > is good for code

On Mon, Oct 14, 2019 at 09:43:25AM +0800, Jason Wang wrote: > > On 2019/10/13 ??4:27, Michael S. Tsirkin wrote: > > On Sat, Oct 12, 2019 at 03:28:49PM +0800, Jason Wang wrote: > > > On 2019/10/11 ??9:45, Michael S. Tsirkin wrote: > > > > The idea is to support multiple ring formats by converting > > > > to a format-independent array of descriptors.

The idea is to support multiple ring formats by converting to a format-independent array of descriptors. This costs extra cycles, but we gain in ability to fetch a batch of descriptors in one go, which is good for code cache locality. To simplify benchmarking, I kept the old code around so one can switch back and forth by writing into a module parameter. This will go away in the final

Hello all, This is one of those "Is there a better way to do this questions". Say I have a dataframe (df) with a grouping variable (z). This is my base data. Now I know that there is a higher order level of grouping that exist for my group variable. So what I want to do is create a new column that express that higher order level of grouping based on values in the sub-group (z in this

So the idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will also allow all kind of batching tricks - e.g. it seems possible to keep SMAP disabled while we are fetching multiple descriptors. And perhaps more importantly,

So the idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will also allow all kind of batching tricks - e.g. it seems possible to keep SMAP disabled while we are fetching multiple descriptors. And perhaps more importantly,

This adds infrastructure required for supporting multiple ring formats. The idea is as follows: we convert descriptors to an independent format first, and process that converting to iov later. The point is that we have a tight loop that fetches descriptors, which is good for cache utilization. This will also allow all kind of batching tricks - e.g. it seems possible to keep SMAP disabled while

I'm not advocating AAA. However this is a proposal for more modern thinking regarding the permissiveness of auto in LLVM codebases. Currently the rule on the use of auto is here: https://llvm.org/docs/CodingStandards.html#use-auto-type-deduction-to-make-code-more-readable It is quite strict. It allows the use of auto for * lambdas * iterators because they are long to type * casts to