On 04/03/2014 06:25 AM, Tom Robinson wrote:
> On 02/04/14 20:17, Alexandru Chiscan wrote:
>> On 04/02/2014 01:00 AM, Tom Robinson wrote:
>>> On 01/04/14 17:49, Alexandru Chiscan wrote:
On 04/01/2014 06:27 AM, Keith Keller wrote:
> On 2014-04-01, Tom Robinson wrote:
>> Now, I understan
On 02/04/14 20:17, Alexandru Chiscan wrote:
> On 04/02/2014 01:00 AM, Tom Robinson wrote:
>> On 01/04/14 17:49, Alexandru Chiscan wrote:
>>> On 04/01/2014 06:27 AM, Keith Keller wrote:
On 2014-04-01, Tom Robinson wrote:
> Now, I understand that Red Hat (and therefore CentOS) backport many
On 04/02/2014 01:00 AM, Tom Robinson wrote:
> On 01/04/14 17:49, Alexandru Chiscan wrote:
>> On 04/01/2014 06:27 AM, Keith Keller wrote:
>>> On 2014-04-01, Tom Robinson wrote:
Now, I understand that Red Hat (and therefore CentOS) backport many upstr=
eam features into the stock
kern
On 01/04/14 17:49, Alexandru Chiscan wrote:
> On 04/01/2014 06:27 AM, Keith Keller wrote:
>> On 2014-04-01, Tom Robinson wrote:
>>> Now, I understand that Red Hat (and therefore CentOS) backport many upstr=
>>> eam features into the stock
>>> kernel so how can I be sure that kernel 2.6.32-431.11.2
On 04/01/2014 06:27 AM, Keith Keller wrote:
> On 2014-04-01, Tom Robinson wrote:
>> Now, I understand that Red Hat (and therefore CentOS) backport many upstr=
>> eam features into the stock
>> kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar=
>> rier support?
Take a look h
On 01/04/14 14:27, Keith Keller wrote:
> On 2014-04-01, Tom Robinson wrote:
>> Now, I understand that Red Hat (and therefore CentOS) backport many upstr=
>> eam features into the stock
>> kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar=
>> rier support?
> I believe you ca
On 2014-04-01, Tom Robinson wrote:
> Now, I understand that Red Hat (and therefore CentOS) backport many upstr=
> eam features into the stock
> kernel so how can I be sure that kernel 2.6.32-431.11.2.el6 has write bar=
> rier support?
I believe you can look through the RHEL tech notes. Here they
Hi,
I've been looking for an answer to this question and can't find anything
concrete that says full
support for write barriers has been backported to the stock kernel.
I've read that:
"There is incomplete write barrier support in kernel versions 2.6.32 and
earlier (2.6.31 has some
support, wh
8 matches
Mail list logo