[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20250304132507.GC26141@redhat.com>
Date: Tue, 4 Mar 2025 14:25:08 +0100
From: Oleg Nesterov <oleg@...hat.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Mateusz Guzik <mjguzik@...il.com>,
K Prateek Nayak <kprateek.nayak@....com>,
"Sapkal, Swapnil" <swapnil.sapkal@....com>,
Manfred Spraul <manfred@...orfullife.com>,
Christian Brauner <brauner@...nel.org>,
David Howells <dhowells@...hat.com>,
WangYuli <wangyuli@...ontech.com>, linux-fsdevel@...r.kernel.org,
linux-kernel@...r.kernel.org,
"Shenoy, Gautham Ranjal" <gautham.shenoy@....com>,
Neeraj.Upadhyay@....com, Ananth.narayan@....com
Subject: Re: [PATCH] pipe_read: don't wake up the writer if the pipe is still
full
On 03/04, Oleg Nesterov wrote:
>
> On 03/03, Linus Torvalds wrote:
> >
> > +/*
> > + * Really only alpha needs 32-bit fields, but
> > + * might as well do it for 64-bit architectures
> > + * since that's what we've historically done,
> > + * and it makes 'head_tail' always be a simple
> > + * 'unsigned long'.
> > + */
> > +#ifdef CONFIG_64BIT
> > + typedef unsigned int pipe_index_t;
> > +#else
> > + typedef unsigned short pipe_index_t;
> > +#endif
>
> I am just curious, why we can't use "unsigned short" unconditionally
> and avoid #ifdef ?
>
> Is "unsigned int" more efficient on 64-bit?
Ah, I guess I misread the comment...
So, the problem is that 64-bit alpha can't write u16 "atomically" ?
Oleg.
Powered by blists - more mailing lists