| To: | Radoslaw Szkodzinski <astralstorm@xxxxxxxxx> |
|---|---|
| Subject: | Re: XFS -git changes and Linux-VServer patch porting |
| From: | Josef Sipek <jsipek@xxxxxxxxxxxxxxxxx> |
| Date: | Wed, 18 Jul 2007 12:42:01 -0400 |
| Cc: | Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, xfs@xxxxxxxxxxx |
| In-reply-to: | <f44c5fdf0707180649h778f017dlb532c3ba224944b2@xxxxxxxxxxxxxx> |
| References: | <f44c5fdf0707180649h778f017dlb532c3ba224944b2@xxxxxxxxxxxxxx> |
| Sender: | xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
On Wed, Jul 18, 2007 at 03:49:07PM +0200, Radoslaw Szkodzinski wrote:
> Linux-VServer patch adds 2 new flags: barrier and iunlink.
> With recent changes in -git (filestreams), XFS now lacks di_flags bits
> to add these.
> iunlink flag adds Copy-on-Write semantics to hard links, while barrier
> flag signifies a filesystem barrier no virtual context can pass.
>
> I'd like to know how to possibly resolve this problem w/o negatively
> impacting performance (especially of iunlink) or changing on-disc
> format in an incompatible way, as well as being more future-proof.
A while back, I mentioned that it would be nice to have a whiteout inode
flag (I've since changed my mind) but the answer I got from Dave Chinner,
et. al., was to use xattrs.
Josef 'Jeff' Sipek.
--
If I have trouble installing Linux, something is wrong. Very wrong.
- Linus Torvalds
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Software RAID5 Horrible Write Speed On 3ware Controller!!, Justin Piszcz |
|---|---|
| Next by Date: | Re: Software RAID5 Horrible Write Speed On 3ware Controller!!, Bryan J. Smith |
| Previous by Thread: | XFS -git changes and Linux-VServer patch porting, Radoslaw Szkodzinski |
| Next by Thread: | tuning XFS for tiny files, timotheus |
| Indexes: | [Date] [Thread] [Top] [All Lists] |